Skip to content
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

Open
Alex-Andr-19 opened this issue Sep 26, 2024 · 4 comments
Open

Change package manager on pnpm #8

Alex-Andr-19 opened this issue Sep 26, 2024 · 4 comments

Comments

@Alex-Andr-19
Copy link

Alex-Andr-19 commented Sep 26, 2024

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 in node_modules and another reason for change npm is install dependencing packages with missmatching of versions.
Example, project has package A with dependency of C with version 1.1.5 and package B with dependency of C with version 1.0.5. Last versioin of C that would be loaded is 1.0.5. npm can create incidence that would be import in package A package C with version 1.0.5, but package A should use newer API of C.

I prefer use package-manager pnpm.

@bezumkin
Copy link
Owner

Sorry, but pnpm is not included in the official Node Docker image we are using. I don't want to create a custom image until I'm forced to do so.

I believe npm is "old, but not obsolete"(c).

@Alex-Andr-19
Copy link
Author

Alex-Andr-19 commented Sep 28, 2024

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.

@alex-skakun
Copy link

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 in node_modules and another reason for change npm is install dependencing packages with missmatching of versions. Example, project has package A with dependency of C with version 1.1.5 and package B with dependency of C with version 1.0.5. Last versioin of C that would be loaded is 1.0.5. npm can create incidence that would be import in package A package C with version 1.0.5, but package A should use newer API of C.

I prefer use package-manager pnpm.

To avoid this kind of issues follow at least next two rules:

  • Install dependencies with fixed version: npm i -E <package_name>.
  • do not use npm install for installing all dependencies, use npm ci for this purpose.

@senyaak
Copy link

senyaak commented Oct 13, 2024

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
Also having different version of the same package is BAD - why would anyone want this...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants