-
Notifications
You must be signed in to change notification settings - Fork 27k
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(test): run all tests against node@21
#57057
base: canary
Are you sure you want to change the base?
Conversation
node@21
node@21
Failing test suitesCommit: 0e48812
Expand output● Has CSS in computed styles in Development › should have CSS for page
Read more about building and testing Next.js in contributing.md.
Expand output● Dynamic Route CSS Module Usage › production mode › should have compiled successfully
● Dynamic Route CSS Module Usage › production mode › should've emitted a single CSS file
● Dynamic Route CSS Module Usage › production mode › should apply styles correctly
● Catch-all Route CSS Module Usage › production mode › should have compiled successfully
● Catch-all Route CSS Module Usage › production mode › should apply styles correctly
● Catch-all Route CSS Module Usage › production mode › should've emitted a single CSS file
Read more about building and testing Next.js in contributing.md.
Expand output● next/dynamic › dev mode › should load page correctly
Read more about building and testing Next.js in contributing.md.
Expand output● SCSS Support loader handling › CSS URL via
● SCSS Support loader handling › CSS URL via
● SCSS Support loader handling › CSS URL via file-loader sass partial › should compile successfully
● SCSS Support loader handling › CSS URL via file-loader sass partial › should've emitted expected files
● SCSS Support loader handling › CSS URL via
● SCSS Support loader handling › CSS URL via
● SCSS Support loader handling › CSS URL via
● SCSS Support loader handling › CSS URL via
● SCSS Support loader handling › Data Urls › should compile successfully
● SCSS Support loader handling › Data Urls › should've emitted expected files
● SCSS Support loader handling › External imports › should compile successfully
● SCSS Support loader handling › External imports › should've emitted expected files
● SCSS Support loader handling › Preprocessor loader order › should compile successfully
Read more about building and testing Next.js in contributing.md.
Expand output● Basic Global Support scss › production mode › should compile successfully
● Basic Global Support scss › production mode › should've emitted a single CSS file
● Basic Module Include Paths Support › production mode › should compile successfully
● Basic Module Include Paths Support › production mode › should've emitted a single CSS file
● Basic Module Prepend Data Support › production mode › should compile successfully
● Basic Module Prepend Data Support › production mode › should've emitted a single CSS file
● Basic Global Support with src/ dir › production mode › should compile successfully
● Basic Global Support with src/ dir › production mode › should've emitted a single CSS file
● Multi Global Support › production mode › should compile successfully
● Multi Global Support › production mode › should've emitted a single CSS file
● Nested @import() Global Support › production mode › should compile successfully
● Nested @import() Global Support › production mode › should've emitted a single CSS file
● Multi Global Support (reversed) › production mode › should compile successfully
● Multi Global Support (reversed) › production mode › should've emitted a single CSS file
● Good CSS Import from node_modules › production mode › should compile successfully
● Good CSS Import from node_modules › production mode › should've emitted a single CSS file
● Good Nested CSS Import from node_modules › production mode › should compile successfully
● Good Nested CSS Import from node_modules › production mode › should've emitted a single CSS file
● CSS Import from node_modules › production mode › should fail the build
Read more about building and testing Next.js in contributing.md.
Expand output● should handle unresolved files gracefully › production mode › should build correctly
● should handle unresolved files gracefully › production mode › should have correct file references in CSS output
Read more about building and testing Next.js in contributing.md.
Expand output● Basic SCSS Module Support › production mode › should have compiled successfully
● Basic SCSS Module Support › production mode › should've emitted a single CSS file
● Basic SCSS Module Support › production mode › should've injected the CSS on server render
● 3rd Party CSS Module Support › production mode › should have compiled successfully
● 3rd Party CSS Module Support › production mode › should've emitted a single CSS file
● 3rd Party CSS Module Support › production mode › should've injected the CSS on server render
● Has CSS Module in computed styles in Development › should have CSS for page
● Has CSS Module in computed styles in Production › production mode › should have compiled successfully
● Has CSS Module in computed styles in Production › production mode › should have CSS for page
● Can hot reload CSS Module without losing state › should update CSS color without remounting
● CSS Module Composes Usage (Basic) › production mode › should have compiled successfully
● CSS Module Composes Usage (Basic) › production mode › should've emitted a single CSS file
● CSS Module Composes Usage (External) › production mode › should have compiled successfully
● CSS Module Composes Usage (External) › production mode › should've emitted a single CSS file
Read more about building and testing Next.js in contributing.md.
Expand output● yarn PnP › should compile and serve the index page correctly with-next-sass
Read more about building and testing Next.js in contributing.md. |
@@ -9,7 +9,7 @@ RUN apt install unzip wget curl nano htop screen build-essential pkg-config libs | |||
|
|||
RUN ln $(which python3) /usr/bin/python | |||
|
|||
RUN curl -sfLS https://install-node.vercel.app/v18.17.0 | bash -s -- -f | |||
RUN curl -sfLS https://install-node.vercel.app/v21 | bash -s -- -f |
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 could make this come from an env variable so it always installs the same version as defined in the workflow with NODE_LTS_VERSION
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.
this might be risky if we're using apis that available in new nodejs version but not supported in 18. we had similar problem before that we were using api that not supported in 16 but available in 17 or 18
@@ -8,7 +8,7 @@ on: | |||
env: | |||
NAPI_CLI_VERSION: 2.16.2 | |||
TURBO_VERSION: 1.10.9 | |||
NODE_LTS_VERSION: 20 | |||
NODE_LTS_VERSION: 21 |
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.
Nit: 21 is not the LTS version, should we rename the variable to avoid ambiguity?
@@ -146,7 +146,7 @@ jobs: | |||
group: [1, 2, 3, 4, 5] | |||
uses: ./.github/workflows/build_reusable.yml | |||
with: | |||
nodeVersion: 18.17.0 | |||
nodeVersion: 21 |
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.
nodeVersion: 21 | |
nodeVersion: ${{github.env.NODE_LTS_VERSION}} |
@@ -211,7 +211,7 @@ jobs: | |||
|
|||
uses: ./.github/workflows/build_reusable.yml | |||
with: | |||
nodeVersion: 18.17.0 | |||
nodeVersion: 21 |
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.
nodeVersion: 21 | |
nodeVersion: ${{github.env.NODE_LTS_VERSION}} |
@balazsorban44 I think this is intentionally a draft pr to test Next.js against the new Node.js version to see what's breaking. See the related Node.js issue in the PR body for more info |
This draft is testing to see if
node@21
passes or fails our existing tests.