Share Dependencies source in one folder like Maven, instead of installing it for each project #276
Unanswered
yasser-mas
asked this question in
RRFC
Replies: 1 comment 5 replies
-
The current mechanism allows you to make local edits in a dependency, without affecting every other project on your machine. Your suggestion (which aligns with yarn 2, pnpm, and tink's approaches) prevents that. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Share Dependencies source in one folder like Maven, instead of installing it for each project.
Maven has
./m2/repository/
directory which has all maven dependencies sources which downloaded from maven repo website classified by package name and version.If any project depending on any dependency during build phase, it will be collected from the local repo otherwise it will be pulled from website to local repo, also it will be available during development phase.
so it would be better if NPM support that instead of installing same dependencies sources in local folder for all projects !!
there are dependencies has large size like angular and electron , why should I duplicate the same dependencies sources in all projects which I have !! .
Beta Was this translation helpful? Give feedback.
All reactions