Maël Nison
Maël Nison
I'd be interested in supporting them - constraints solve some of the same issues, but I think both can coexist. Reusing dependencies across a project is a common need, it...
At the moment I'm focusing on some major refactoring for a future major release, so I didn't get the chance to implement it yet. Help would be appreciated here!
> In a project subdirectory (I'm not, I'm in `~/projects/asdfsadfg`) You probably have a bogus `yarn.lock` in `~` or `~/projects`.
Out of curiosity, what did you use instead?
You added a test fixture but I think you forgot the test itself
The main reason I didn't alias it at the moment is that the commands are subtly different: `upgrade` used to upgrade only in the current workspace (and thus wasn't much...
Yep, it's a tricky one 🤔 It worked in npm / Yarn 1 because the shell only runs symlinks if the underlying file actually exists, whether in our case the...
Looking at the `node` package in more detail, I'm not sure it'll be possible to make it compatible. The way it is written is very strange: - The postinstall calls...
I don't follow - you have `axios` in your `dependencies`, why shouldn't `--environment production` report it?
Oh, I see, thanks for explaining! Yes indeed, it seems to be a legit bug.