`next build` setting packageManager in package.json
Unanswered
Spectacled bear posted this in #help-forum
Spectacled bearOP
In my work's monorepo I noticed that whenever I run
I'm not using yarn, and I didn't setup next with yarn. I reproduced this very simply in this repo, just clone it, and run next build in the next directory. All I did was create a vanilla next app and set it up as a npm workspace.
https://github.com/bluefeet/next-sets-package-manager
Any idea what's going on?
next build the repo root's package.json would have this line added:"packageManager": "yarn@1.22.22+sha512.a6b2f7906b721bba3d67d4aff083df04dad64c399707841b7acf00f6b133b7ac24255f2652fa22ae3534329dc6180534e98d17432037ff6fd140556e2bb3137e"I'm not using yarn, and I didn't setup next with yarn. I reproduced this very simply in this repo, just clone it, and run next build in the next directory. All I did was create a vanilla next app and set it up as a npm workspace.
https://github.com/bluefeet/next-sets-package-manager
Any idea what's going on?
1 Reply
Spectacled bearOP
If I manually set
packageManager to something at least next build doesn't overwrite it. So that's what I'll do in my work repo - set it to npm. But, this is still a funky side-effect of running next build.