Absolute paths in pnpm-lock.yml when using resolutions about pnpm HOT 3 CLOSED

We should be able to fix this probably.

v9 is in alpha and does not work yet for us, so we are using the latest version of v8 as of last week.

What doesn't work with v9?

from pnpm.

The idiomatic pnpm workflow is pnpm-workspace.yaml and workspace scheme (workspace:*). Is there a reason that you must use file:?

from pnpm.

We should be able to fix this probably.

v9 is in alpha and does not work yet for us, so we are using the latest version of v8 as of last week.

What doesn't work with v9?

Thank you for looking at this! To answer your question, this is the error I get trying to run 9.0.0-alpha.0. It's strange, because our node version is greater than what is listed.

ERROR: This version of pnpm requires at least Node.js v16.14
The current version of Node.js is v16.15.1
Visit https://r.pnpm.io/comp to see the list of past pnpm versions with respective Node.js version support.

The idiomatic pnpm workflow is pnpm-workspace.yaml and workspace scheme (workspace:*). Is there a reason that you must use file:?

Our build system was previously designed with --preserve-symlinks which does not work with PNPM, so we've been converting everything to work without this flag. However, some logic still relied on the old behavior, so using file: "hardlink" instead of "symlink" is helping us to work around the issue in the short term until we can update our build system. Sometimes we also want to override a package from the NPM feed with a local copy, and did this previously in yarn with no issues with the lock file (it only used relative path from workspace root), so I'm optimistic whether PNPM could support this scenario.

from pnpm.