You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't necessarily an issue with pnpm but unfortunately trying to install this package globally (to use with editor lsp integration) causes the lockfile to become malformed once the engine field is parsed.
It's really annoying that they enforce this dependency on Yarn (there are more than 2 package managers... 😢 ) but I suppose pnpm will probably want to have some sanity checks for this sort of stuff as well.
The text was updated successfully, but these errors were encountered:
pnpm version: 6.6.2
Code to reproduce the issue:
Expected behavior:
The lockfile is not broken, or the package is not committed to the lockfile if strict engine parsing is used.
Actual behavior:
As for the actual lockfile contents:
Additional information:
node -v
prints: v16.2.0To clarify, the issue here is that
yaml-language-server
package puts some newlines into its engines field, as seen here:https://github.com/redhat-developer/yaml-language-server/blob/master/package.json#L22
This isn't necessarily an issue with pnpm but unfortunately trying to install this package globally (to use with editor lsp integration) causes the lockfile to become malformed once the engine field is parsed.
It's really annoying that they enforce this dependency on Yarn (there are more than 2 package managers... 😢 ) but I suppose pnpm will probably want to have some sanity checks for this sort of stuff as well.
The text was updated successfully, but these errors were encountered: