Emanuele Stoppa

I agree with you that setting the registry for ALL the packages should lead to this behaviour (which is correct). Although, as you said, npm falls back to the default...

Yes, that would help too I think! Maybe a suggestion to add the package scope in the `registry` key inside the `.npmrc`

@juanpicado I have tried with npm 6 (can't recall which version). I will try with npm 7 once I get the chance and let you know how it behaves.

I am interested at this topic. Now that Babel supports typescript, I'm more keen to use Babel as compiler and use typescript as just type checker. Although I hit a...

Are there any updates about this? I would like to give some help, maybe starting proposing a prototype

That's a strange situation though. There are people that are willing to give time to help developing a new solution but you don't want to accept it (https://github.com/19majkel94/type-graphql/pull/304#issuecomment-480621261). So you're...

If everyone agrees, we could have an upstream branch and you could make PRs against that branch. We can create an issue with the detailed list of the things to...

I created the upstream breanch `webpack-cli-ui`. All the PRs regarding this project should go against that branch

Feel free to discuss here if you prefer https://github.com/webpack/webpack-cli/issues/647 As Even suggested, feel free to create issues and PRs! We will make sure to pin them to the UI project...

Try go give a try to `execa`, package to handle child processes. We introduced in one of the PRs and maybe it could help you solving your issue. For testing,...