-
Notifications
You must be signed in to change notification settings - Fork 36
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
Breaking Changes #1
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Ray,
When running npm install I initially received lots of security warnings from npm audit.
The reason for this is because you have set up your package.json to pull the latest major version of each of the project dependencies, which are now causing breaking changes.
I suggest the best way to resolve this is to change the ^ prefix to ~ this will only then pull the latest minor (non breaking changes). You could also simply remove the prefix altogether and NPM will only pull the exact version of the file you've specified.
HTH
Rob
The text was updated successfully, but these errors were encountered: