I noticed that since 3.3.0, the package.json file has terabox-node as a dependency of itself. At least on my machine, this led to a recursion after installation, with terabox-node containing node_modules, which contains terabox-node, which contains node_modules, which contains terabox-node, ... Is this intended? When I removed terabox-node from the dependency list and re-installed, terabox-node still seemed to function well. This is on Windows 11, with node 25.9.0 and pnpm 10.33.0.
I noticed that since 3.3.0, the package.json file has terabox-node as a dependency of itself. At least on my machine, this led to a recursion after installation, with terabox-node containing node_modules, which contains terabox-node, which contains node_modules, which contains terabox-node, ... Is this intended? When I removed terabox-node from the dependency list and re-installed, terabox-node still seemed to function well. This is on Windows 11, with node 25.9.0 and pnpm 10.33.0.