David Michon

My concern about `package.json` being a generated file is that many editors have special auto-complete behavior for package.json in particular, and that other tools in the workspace that you could...

I'm now proposing https://github.com/pnpm/pnpm/issues/3816 as the preferred package manager support, since it also works to support alternate publishing conventions (e.g. having the authoritative local version specifier for a package live...

One opportunity of having `package.json` be a generated file is that it allows us to write different versions of `package.json` at build time vs. publish time, e.g. so that the...

Minimally we may want to remove the fallback to the javascript implementation of `tar`, since the main difference is that the latter accepts invalid tarballs. This should then allow it...

Ideally all of common/temp should probably be ignored by the vscode watcher

It appears webpack 4 is incompatible with node 18 at present

One important change this is going to require is that the scheduler will need to support the concept of operations with retriable failures. I've previously encountered a case where this...

A read from or write to the build cache are both good examples of retriable failures that should have timeouts, yes. The experiment I was doing with install stopped using...

Can we just put these options in a separate file, whose schema is not tracked by Rush (so that new options added to pnpm don't require updates to Rush to...

`git hash-object` is only called on items that show up in `git status`, so this error should only occur if you have locally modified the symbolic link in question and...