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
Compatibility - NPM fails to install project #142
Comments
Thanks for your interest in this project ❤️ ! We use pnpm to ensure a consistent experience among developers and first-level support for workspaces. You can quickly install pnpm(or yarn) through The debate over using npm or pnpm has been ongoing for quite some time, but the advantages offered by pnpm will far outweigh its limitations. Regardless, if you have any topics of interest, let's continue the discussion. |
Hi team - I'm probably going to be annoying with issues over the next few days as I explore but the very first thing I noticed is the inability to install via NPM in any way:
While I respect the opinion to use ni (I had not heard of it), it's a bit of a barrier to teams who purposely choose to stick close to the "approved" ecosystem. In my case, I have to provide details of our CI/CD pipeline to people who might not love / may not yet have vetted
pnpm
, etc. So being unable to use the out-of-boxnpm
candidate is a pain point. Worse yet, version locking in our ecosystem is provided by fnm so the cache benefits ofpnpm
actually end up being a bit of a security detriment.We run relatively strict development environments and I can tell you from experience that the requirement for
pnpm
would restrict more enterprise-oriented development contributions to the project. In our case, our app containers don't even havepnpm
so to contribute to the project, we would need to modify the base images themselves which is obviously a barrier.Recommendation:
npm
for official published variations ORnpm
itself works to install the reponpm i --package-lock-only
Workspaces - which seems to be the primary draw of
pnpm
here - are supported in the latest NPM (perhaps not as exhaustively).I'm sure you guys will close this as a TODO (I probably would) but it does mean I'm not going to be able to contribute to a codebase I am very interested in helping along the way.
The text was updated successfully, but these errors were encountered: