We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
B
With the npm 7 version some breaking changes are introduced
Run npm install on a fresh cloned repo in the frontend folder
The user should not be forced to use the --legacy-peer-deps
--legacy-peer-deps
The text was updated successfully, but these errors were encountered:
petrican
No branches or pull requests
Is this a bug or feature request?
B
What is the current behavior?
With the npm 7 version some breaking changes are introduced
Which are the steps to reproduce?
Run npm install on a fresh cloned repo in the frontend folder
What is the expected or desired behavior?
The user should not be forced to use the
--legacy-peer-deps
The text was updated successfully, but these errors were encountered: