Zoltan Kochan

In v7 the file protocol always works as injected. For the old behavior of `file:`, use `link:` instead.

This is the same way it works in Yarn.

Well, you said "I can't use link because users might be using yarn or npm" but as I said, the file: protocol works the same way in both pnpm v7...

It might be that the build overwrites the files in the package. In that case, only some "sync" command would help.

As I already said above, the `file:` protocol works the same in both pnpm and Yarn. It worked the same way in npm as well (until version 5). I don't...

> if I choose pnpm a lot of users will complain. I don't get it. Do contributors to the project complain? Contributors to your repositories? > why was it working...

Maybe. I don't know

It is probably because pnpm switched to the latest version of node-gyp. Maybe we can [make it configurable](https://github.com/pnpm/pnpm/issues/405)

As a workaround, just add the older version of node-gyp to the dependencies of the package that fails. You can do that using [packageExtensions](https://pnpm.io/package_json#pnpmpackageextensions) For instance: ``` "pnpm: { "packageExtensions":...

@fatso83 I'll check your issue later.