-
Notifications
You must be signed in to change notification settings - Fork 27.4k
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
Support node-sass@6 #28710
Support node-sass@6 #28710
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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.
Looks like this is breaking a bunch of tests.
Hi @timneutkens, indeed it does! I will investigate but have never touched this part of the code before, so any help would be appreciated :) |
@timneutkens It seems I also needed to bump sass-loader to 10.2.0, which still supports Webpack@4, but also supports Node@16. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
…xt.js into feat/support-node-sass-6
I've updated the precompiled dependency (sass-loader), then the tests should pass 👍 |
Thank you! Could you please tell me how you did it? This way I will be able to do it myself next time :) |
This comment has been minimized.
This comment has been minimized.
We generally run these ourselves to ensure there's no compilation difference 👍 |
I am under the impression the 2 remaining tests are not failing because of my changes. Can you confirm? |
Correct! |
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.
Thanks! This looks good to land now 👍
This comment has been minimized.
This comment has been minimized.
Failing test suitesCommit: bc7ffb7 test/integration/config-devtool-dev/test/index.test.js
Expand output● devtool set in development mode in next config › should warn and revert when a devtool is set in development mode
|
Stats from current PRDefault Build (Increase detected
|
vercel/next.js canary | adrienharnay/next.js feat/support-node-sass-6 | Change | |
---|---|---|---|
buildDuration | 14.1s | 14.3s | |
buildDurationCached | 3.6s | 3.6s | -73ms |
nodeModulesSize | 48.2 MB | 48.2 MB |
Page Load Tests Overall increase ✓
vercel/next.js canary | adrienharnay/next.js feat/support-node-sass-6 | Change | |
---|---|---|---|
/ failed reqs | 0 | 0 | ✓ |
/ total time (seconds) | 2.761 | 2.804 | |
/ avg req/sec | 905.32 | 891.62 | |
/error-in-render failed reqs | 0 | 0 | ✓ |
/error-in-render total time (seconds) | 1.499 | 1.482 | -0.02 |
/error-in-render avg req/sec | 1667.43 | 1687.38 | +19.95 |
Client Bundles (main, webpack, commons)
vercel/next.js canary | adrienharnay/next.js feat/support-node-sass-6 | Change | |
---|---|---|---|
745.HASH.js gzip | 179 B | 179 B | ✓ |
framework-HASH.js gzip | 42.2 kB | 42.2 kB | ✓ |
main-HASH.js gzip | 23.3 kB | 23.3 kB | ✓ |
webpack-HASH.js gzip | 1.45 kB | 1.45 kB | ✓ |
Overall change | 67.2 kB | 67.2 kB | ✓ |
Legacy Client Bundles (polyfills)
vercel/next.js canary | adrienharnay/next.js feat/support-node-sass-6 | Change | |
---|---|---|---|
polyfills-a4..dd70.js gzip | 31 kB | 31 kB | ✓ |
Overall change | 31 kB | 31 kB | ✓ |
Client Pages
vercel/next.js canary | adrienharnay/next.js feat/support-node-sass-6 | Change | |
---|---|---|---|
_app-HASH.js gzip | 979 B | 979 B | ✓ |
_error-HASH.js gzip | 194 B | 194 B | ✓ |
amp-HASH.js gzip | 312 B | 312 B | ✓ |
css-HASH.js gzip | 329 B | 329 B | ✓ |
dynamic-HASH.js gzip | 2.67 kB | 2.67 kB | ✓ |
head-HASH.js gzip | 351 B | 351 B | ✓ |
hooks-HASH.js gzip | 918 B | 918 B | ✓ |
image-HASH.js gzip | 4.14 kB | 4.14 kB | ✓ |
index-HASH.js gzip | 261 B | 261 B | ✓ |
link-HASH.js gzip | 1.66 kB | 1.66 kB | ✓ |
routerDirect..HASH.js gzip | 318 B | 318 B | ✓ |
script-HASH.js gzip | 387 B | 387 B | ✓ |
withRouter-HASH.js gzip | 320 B | 320 B | ✓ |
bb14e60e810b..30f.css gzip | 125 B | 125 B | ✓ |
Overall change | 13 kB | 13 kB | ✓ |
Client Build Manifests
vercel/next.js canary | adrienharnay/next.js feat/support-node-sass-6 | Change | |
---|---|---|---|
_buildManifest.js gzip | 492 B | 492 B | ✓ |
Overall change | 492 B | 492 B | ✓ |
Rendered Page Sizes
vercel/next.js canary | adrienharnay/next.js feat/support-node-sass-6 | Change | |
---|---|---|---|
index.html gzip | 539 B | 539 B | ✓ |
link.html gzip | 552 B | 552 B | ✓ |
withRouter.html gzip | 533 B | 533 B | ✓ |
Overall change | 1.62 kB | 1.62 kB | ✓ |
Webpack 4 Mode (Decrease detected ✓)
General Overall increase ⚠️
vercel/next.js canary | adrienharnay/next.js feat/support-node-sass-6 | Change | |
---|---|---|---|
buildDuration | 11.6s | 11.6s | |
buildDurationCached | 4.8s | 4.8s | -15ms |
nodeModulesSize | 48.2 MB | 48.2 MB |
Page Load Tests Overall decrease ⚠️
vercel/next.js canary | adrienharnay/next.js feat/support-node-sass-6 | Change | |
---|---|---|---|
/ failed reqs | 0 | 0 | ✓ |
/ total time (seconds) | 2.797 | 2.781 | -0.02 |
/ avg req/sec | 893.88 | 898.8 | +4.92 |
/error-in-render failed reqs | 0 | 0 | ✓ |
/error-in-render total time (seconds) | 1.497 | 1.517 | |
/error-in-render avg req/sec | 1670.45 | 1647.55 |
Client Bundles (main, webpack, commons)
vercel/next.js canary | adrienharnay/next.js feat/support-node-sass-6 | Change | |
---|---|---|---|
16.HASH.js gzip | 186 B | 186 B | ✓ |
677f882d2ed8..HASH.js gzip | 14.1 kB | 14.1 kB | ✓ |
framework.HASH.js gzip | 41.9 kB | 41.9 kB | ✓ |
main-HASH.js gzip | 10.7 kB | 10.7 kB | ✓ |
webpack-HASH.js gzip | 1.19 kB | 1.19 kB | ✓ |
Overall change | 68.1 kB | 68.1 kB | ✓ |
Legacy Client Bundles (polyfills)
vercel/next.js canary | adrienharnay/next.js feat/support-node-sass-6 | Change | |
---|---|---|---|
polyfills-a4..dd70.js gzip | 31 kB | 31 kB | ✓ |
Overall change | 31 kB | 31 kB | ✓ |
Client Pages
vercel/next.js canary | adrienharnay/next.js feat/support-node-sass-6 | Change | |
---|---|---|---|
_app-HASH.js gzip | 964 B | 964 B | ✓ |
_error-HASH.js gzip | 3.8 kB | 3.8 kB | ✓ |
amp-HASH.js gzip | 552 B | 552 B | ✓ |
css-HASH.js gzip | 333 B | 333 B | ✓ |
dynamic-HASH.js gzip | 2.87 kB | 2.87 kB | ✓ |
head-HASH.js gzip | 3.06 kB | 3.06 kB | ✓ |
hooks-HASH.js gzip | 924 B | 924 B | ✓ |
index-HASH.js gzip | 231 B | 231 B | ✓ |
link-HASH.js gzip | 1.64 kB | 1.64 kB | ✓ |
routerDirect..HASH.js gzip | 298 B | 298 B | ✓ |
script-HASH.js gzip | 3.03 kB | 3.03 kB | ✓ |
withRouter-HASH.js gzip | 295 B | 295 B | ✓ |
30809af5c834..565.css gzip | 125 B | 125 B | ✓ |
Overall change | 18.1 kB | 18.1 kB | ✓ |
Client Build Manifests
vercel/next.js canary | adrienharnay/next.js feat/support-node-sass-6 | Change | |
---|---|---|---|
_buildManifest.js gzip | 500 B | 500 B | ✓ |
Overall change | 500 B | 500 B | ✓ |
Rendered Page Sizes
vercel/next.js canary | adrienharnay/next.js feat/support-node-sass-6 | Change | |
---|---|---|---|
index.html gzip | 585 B | 585 B | ✓ |
link.html gzip | 597 B | 597 B | ✓ |
withRouter.html gzip | 578 B | 578 B | ✓ |
Overall change | 1.76 kB | 1.76 kB | ✓ |
I can't seem to find this commit on v11.1.3. Was this PR purposefully omitted from the v12.0.1 backport? The release notes are a bit vague, but looking deeper into it, it looks like only #32092 is featured in 11.1.3. In order to get node v16 support is an update to at least 12.0.5? Note: I can see the commit on v11.1.3-canary.105 Could it be possible that the commit was accidentally omitted? |
Please see #34139 (comment) |
This features supports node-sass@6, which supports node@16.
Addresses the discussion #28704 (comment)