-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible dependency conflict #412
Comments
Reproduced on my environment
I will work on this 😁 |
@rodrigondec seems not related. I agree that supporting only one package manager is better in this sense. But the conflict of this issue was probably caused due to some kind of update to eslint or something like that. Probably updating |
I asked about only one package manager because yarn is better than npm at solving dependency conflicts. As it is, it's possible to do
So I shall drop npm support as it can be agreed upon
Additionally, should resolve dependencies to avoid the yarn warning?Or the show can go on? 🤣 |
-- Bug Report --
Expected Behavior
npm install
ormake setup
should execute successfully without flagsCurrent Behavior
It returns this in
stderr
:Steps to Reproduce
Not sure if this occurs in any environments, seems to run ok in my docker.
Using w10 enterprise, node v14.16.0 managed by
nvm
(https://github.com/coreybutler/nvm-windows)The text was updated successfully, but these errors were encountered: