Why packages are not automatically hoisted.

[S-Nakib]

We can install packages inside subdirectories. But they are not automatically hoisted to the root node_modules folder. But after an npm install command from the root, the nested packages are hoisted to the root node_modules folder if there is no other version of the same package.

It would be better if the packages were hoisted without the extra command.

[ruyadorno]

hi @S-Nakib is this in the context of workspaces? As long as there is no package.json file inside the subdirectory everything should always be installed to the root node_modules folder.

[S-Nakib]

Yes @ruyadorno , it is in the context of workspaces. Here every workspace has a package.json file. But still, the packages are first get installed in the workspace's node_modules folder. An npm install command from the root hoists the packages.

[ruyadorno]

Thanks @S-Nakib 👍 in this initial phase of workspaces support the best way to add dependencies to your workspaces is by manually adding it to their package.json files and then running npm install from the root folder.

You may keep an eye on this RFC: #117 that outlines the support to running more commands in the context of each workspace and should provide a better cli workflow for installing dependencies within them.

[S-Nakib]

Thanks a lot, @ruyadorno . But for now, I find it more easy/suitable to add packages by running npm install package-name on workspaces which add the packages on nested/workspace's node_modules folder, and then finally running npm install on the root which will hoist all the packages from the workspace's node_modules folder. Manually editing package.json is kinda painful for me. I hope this also works as well.

[ruyadorno]

for future reference, in case anyone lands on this discussion, starting on [email protected] you can now add dependencies to your workspaces using the -w config option.

For example, adding the package express to a workspace named workspace-a:

$ npm install express -w workspace-a

[its-dibo]

for me, runnin npm i from root, some devDependencies of the workspace are hoisted to the root and other are installed in the workspace instead of hoisting them to the root even if no conflicting in /node_module.

I want all devDependencies to be hoisted, but I don't know how?

[mycarrysun]

Did you ever figure this out?

[mycarrysun]

Would be nice to have a page in the docs explaining why certain things get hoisted and others don't. It's really hard to decipher.

[its-dibo]

for this repo as an example, running npm i from root, the package jsdom and other packages are installed in projects/ngx-cms even if there is no any conflict between those packages and root packages (jsdom dosn't listed in root's dependencies)

is there a method or a command to know why npm selected a specified dir to install the packages into?