-
Notifications
You must be signed in to change notification settings - Fork 116
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
Chore: Upgrade deps and scripts to work with node 10 #893
Conversation
Verified that @jstoffan has signed the CLA. Thanks for the pull request! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have some logic in our release script to enforce a node version iirc, can you double check that will still work? /box/box-content-preview/build/validateNodeVersion.js
Good catch, @jeremypress. I ran the script and didn't see any output. It looks like it's checking the minimum version, which shouldn't conflict with upgrading to node 10. Seems like everything's okay. |
@@ -0,0 +1 @@ | |||
registry=https://registry.npmjs.org/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
weird that this was missing before :O
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in other projects we have both yarnrc and npmrc with this
3de770d
3de770d
to
25e6561
Compare
I also added an
.npmrc
file and package.jsonengines
declaration to replace the current version-checking script.