You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a module defined in a folder. It has it own package.json and a node_modules folder that contains other-lib dependency. The other-lib dependency is not pushed in any registry.
If I install my-lib from the folder with npm install ./my-lib-folder in an existing project, the node_module/other-lib folder is removed.
Expected Behavior
The node_modules folder from the module my-lib should not be removed. If i run npm pack in the my-lib folder, the node_modules/other-lib folder is kept. Also, if I push my-lib to a registry and I install it via npm install the node_modules/other-lib folder is still present.
Steps To Reproduce
See comment below.
Environment
npm: 10.5
Node.js: v18.18.1
OS Name: OS Ventura
The text was updated successfully, but these errors were encountered:
In the ./sdk folder you can see a dependency that has a bundled dependency "genezio-remote".
Steps to reproduce:
Run npm install ./sdk. This will produce the first weird behaviour since it creates a symlink to my folder. This is against what I understand from the npm documentation:
npm install <folder>:
If <folder> sits inside the root of your project, its dependencies will be installed and may be hoisted to the top-level node_modules as they would for other types of dependencies. If <folder> sits outside the root of your project, npm will not install the package dependencies in the directory <folder>, but it will create a symlink to <folder>.
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
I have a module defined in a folder. It has it own
package.json
and anode_modules
folder that containsother-lib
dependency. Theother-lib
dependency is not pushed in any registry.If I install
my-lib
from the folder withnpm install ./my-lib-folder
in an existing project, thenode_module/other-lib
folder is removed.Expected Behavior
The
node_modules
folder from the modulemy-lib
should not be removed. If i runnpm pack
in themy-lib
folder, thenode_modules/other-lib
folder is kept. Also, if I pushmy-lib
to a registry and I install it vianpm install
thenode_modules/other-lib
folder is still present.Steps To Reproduce
See comment below.
Environment
The text was updated successfully, but these errors were encountered: