-
-
Notifications
You must be signed in to change notification settings - Fork 496
Drop support for Node versions less than 16.20.2 #650
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
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
e3af8de
Configure development node version to use v22.x
valscion b1ea834
Configure node version in package.json to require latest node 16.x LTS
valscion 44320f8
Update lockfiles after npm install with node v22.x
valscion 5073986
Update babel and webpack packages, dropping support for Node.js < v16
valscion 25133aa
Update CI to run with node LTS v16.x and higher
valscion 95f2168
Update tests and skip troublesome ones
valscion 98690bf
Mention Node.js support drop as a breaking change
valscion 2929e38
Update test badges in README.md
valscion 377aa2b
Try running Node.js v18.x in CI
valscion 249b674
Revert "Try running Node.js v18.x in CI"
valscion File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
v22.14.0 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I suppose this
@babel/plugin-proposal-class-properties
was necessary after all and its removal caused the error you were seeing @dcsaszar. Maybe we should be using https://babeljs.io/docs/babel-plugin-proposal-decorators instead with some option that makes sense?I'm not too familiar with the view code that uses these decorators. But we'd need to resolve that problem before I can release a new major version.
Uh oh!
There was an error while loading. Please reload this page.
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.
The mobx integration that is used in different places in the UI code seem to rely on decorators. I'm not too familiar with them but they probably need some looking into to make this library still work.
webpack-bundle-analyzer/client/store.js
Lines 9 to 14 in 544a669
webpack-bundle-analyzer/client/components/ModulesTreemap.jsx
Lines 35 to 36 in 544a669
webpack-bundle-analyzer/client/components/ModulesTreemap.jsx
Line 177 in 544a669
webpack-bundle-analyzer/client/components/ModulesTreemap.jsx
Line 181 in 544a669
webpack-bundle-analyzer/client/components/ModulesTreemap.jsx
Line 185 in 544a669
webpack-bundle-analyzer/client/components/ModulesTreemap.jsx
Line 198 in 544a669
webpack-bundle-analyzer/client/components/ModulesTreemap.jsx
Line 202 in 544a669