-
Notifications
You must be signed in to change notification settings - Fork 481
fix(js): test on node versions 20 through 22; 23 is currently broken #1995 #1988
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
Conversation
fa677b9
to
7aab58c
Compare
0194928
to
7bfd67f
Compare
7bfd67f
to
26043fe
Compare
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.
One comment on Node versions to test, but I'll leave to @pavelgj to decide if we want to do this for sure.
Maybe you all already discussed, and I am an outlier here... but... can we separate out the toolchain changes from the style changes into separate PRs? Some of the changes in formatting seem good. But others seem superfluous, and some even go against the style guide. Particularly, removing parens around all of the arrow functions goes against:
And is a huge part of the overall diff here. |
I'm a little caught by surprise here.... |
ca47587
to
8b41fb4
Compare
Fixed. I'll separate the toolchain changes from the formatting for easier review as well. |
4x-12x for our codebase is a significant speed up with no loss of functionality.
I'll keep prettier in this PR and continue the discussion on [discord] |
8b41fb4
to
89751cf
Compare
How do I trigger the pending CI checks? It looks like they are stalled. |
89751cf
to
5b7e623
Compare
…1995 ISSUE: #1995 CHANGELOG: - [x] Update biome configuration to use arrow function arg parens always. - [x] Update github workflows to test on node versions 20 through 22. - [x] We will add version #23 post fixes. - [x] Set node 22 to be the default for our eng workstations in the setup script for now. The configuration for the formatting is more or less based on the Google TypeScript formatting guidelines at: - [x] https://google.github.io/styleguide/tsguide.html#string-literals - [x] https://google.github.io/styleguide/jsguide.html - [x] https://google.github.io/styleguide/tsguide.html#arrow-function-bodies - [x] https://google.github.io/styleguide/tsguide.html#automatic-semicolon-insertion
5b7e623
to
1dd1826
Compare
fix(js): test on node versions 20 through 22; 23 is currently broken #1995
ISSUE: #1995
CHANGELOG:
setup script for now.
REFERENCES:
The configuration for the formatting is more or less based on the Google
TypeScript formatting guidelines at:
Checklist (if applicable):