-
Notifications
You must be signed in to change notification settings - Fork 213
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
Remove node 8 support #1119
Remove node 8 support #1119
Conversation
This pull request has been linked to Shortcut Story #127975: Drop Node 8 support to eliminate a security risk. |
This introduces some warnings from older packages that are no longer maintained. Will revisit them later in this branch.
If I am reading this correctly it shouldn't be necessary any longer as it should be respecting the devtool setting
0adfae0
to
e56f09b
Compare
@waltjones we talked about possibly vendorizing |
I think removing Node 8 clears the way to upgrade to a newer webpack, karma, etc. and then we don't need this package. That said, I wouldn't be opposed to vendorizing in the short term. Sooner than later we should update the main build/CI deps. |
@waltjones I would agree, how would you feel about splitting the deprecation of Node 8 support from upgrading webpack/karma/etc? Make this the official break leaving us more free to select what the next step is |
👍 Agreed. |
…ve-node-8-support
…pport Remove node 8 support
Description of the change
Remove support for node 8, and update dependencies as we are able to.
Type of change
Related issues
Checklists
Development
Code review