-
Notifications
You must be signed in to change notification settings - Fork 4
chore: migrated to package manager to pnpm #204
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
Conversation
🦋 Changeset detectedLatest commit: 51df6e3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
This is even showing errors that does not show with npm. |
I didn't experience that when I cloned and installed the repo. Would it help if we just regenerated the What version of |
|
Already did. Same version. With pnpm another issue appeared through the CI, and were not showing before with npm. Clearly pnpm are working properly where npm was not. |
…replace-package-manager
|
And more. |
|
I would like for you to create an issue for the NPM issue which prompted you to want to migrate to PNPM in the first place, I'm fairly certain we could fix that without migrating package manager. Some of the issues you're seeing might come from:
|
|
https://pnpm.io/cli/recursive#--no-sort Weird that you do not prefer better tooling. As one can easily replace one for another, if ever needed. I gave the reasons in the PR. Not looking to resolve the issues in the current, but actual improve while resolving some that I mentioned. pnpm are clearly more functional than npm. |
Not weird at all - we're the ones maintaining this package in the long run and choosing technology / tools aren't soly about choosing the seemingly superior solution in my experience. To be clear, I'm not saying that NPM is flawless nor that we won't make a switch to a different package manager and I'm not looking to get more into that conversation right now.
I disagree, as I'm unable to reproduce the issue: You're not providing specific commands and outputs from running those and therefore I'm unable to get a strong signal, giving me a compelling reason to accept your suggested change. |
|
@kraenhansen Given your last message, I answered but no response were given, should I assume that this PR is not wanted / needed? |
Right. Without a clearly defined need, I don't see us merging this any time soon 👍 |
Before I had trouble using
npm iin the root, ferric-cli were not running, it wasnt finding the js.Even if it were recognized in the package-lock as workspace installed.
It only worked after I did a
pnpm istraight in the ferric folder, then I was able to run the command standalone. That's the experience I had.This led to this PR. Which in fact work now just after a
pnpm installin the root folder.pnpmare faster, in my experience, there is no reason to not migrate to it, even more if fromnpm.https://pnpm.io/pnpm-vs-npm
https://refine.dev/blog/pnpm-vs-npm-and-yarn/ - Faster CI installs and more