[FEATURE] Support for monorepo dependency installations with NPM

[danielleadams]

What / Why

Has there been progress on any sort of monorepo dependency support? (Such as a Yarn workspace-adjacent feature)

There was a conversation on npm.community (here: https://npm.community/t/npm-needs-a-more-robust-story-for-local-multi-module-development/1059/2) that stated it was in the works, and I wanted to make sure this made it back here for discussion as there are some people still awaiting this feature. While this particular issue that's linked is referring to local development, it points to the larger functionality for monorepos.

When

• n/a

Where

• n/a

How

• I'm not sure

Current Behavior

There isn't support for this specific functionality. There are a few workarounds - one being traversing through each directory with a package.json and installing/updating the node modules.

Expected Behavior

Running an npm install/npm ci will create/reference a single root package-lock.json file and populate the node modules for a subdirectories of the mono repo.

Similar to yarn workspaces, there would be a way to reference subdirectories to each other also (although, this could be a separate feature).

Example:

- /app
  - package.json
  - package-lock.json // -> resolves dependencies from root dir and sub dirs
  - /subdir1
    - package.json
  - /subdir2
    - package.json // -> dependency of "subdir1"

Who

• I'm not sure

References

• Related to: https://yarnpkg.com/lang/en/docs/workspaces/

[ruyadorno]

@danielleadams I think you should def join the npm workspaces discussion 😊

[danielleadams]

@ruyadorno awesome! Happy to look over and contribute in the next few days... excited to see a conversation around this 👍

[ruyadorno]

awesome 😄 I'm going to go ahead and close this issue as I think it's more productive to continue the conversation over there. Thanks!