-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change package manager on pnpm #8
Comments
Sorry, but I believe |
You can just install pnpm in your image and docker will just cache it. You can do it on step after clone node image and cache the installation of pnpm would be saved by long time. |
To avoid this kind of issues follow at least next two rules:
|
pnpm uses npm.. all the issues you can have - are created because you dont know how to use the tool, not because the tool is old :D |
Project's package manager is
npm
, but this technology is so old and has many misstakes on optimisation case. It creates many duplicates of the same packages innode_modules
and another reason for changenpm
is install dependencing packages with missmatching of versions.Example, project has package
A
with dependency ofC
with version 1.1.5 and packageB
with dependency ofC
with version 1.0.5. Last versioin ofC
that would be loaded is 1.0.5.npm
can create incidence that would be import in packageA
packageC
with version 1.0.5, but packageA
should use newer API ofC
.I prefer use package-manager
pnpm
.The text was updated successfully, but these errors were encountered: