-
Notifications
You must be signed in to change notification settings - Fork 27.2k
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
Add sassOption implementation
to support sass-embedded
#64577
Conversation
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/sass-loader@12.4.0 |
af02168
to
e27875a
Compare
e27875a
to
8d08562
Compare
implementation
to support sass-embedded
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
2 similar comments
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
import { colorToRgb } from 'next-test-utils' | ||
|
||
describe('Basic Module Prepend Data Support', () => { | ||
const { next } = nextTestSetup({ |
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.
In order to be sufficient I think we have to duplicate the entire Sass test suite run to also use sass-embedded. Should be pretty straightforward now that these are in test/e2e/app-dir/scss
, could just add a describe.each
around the setup to swap the implementation.
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.
Added tests, see 652602d
652602d
to
5dd58f6
Compare
|
test/e2e/app-dir/scss/compilation-and-prefixing/compilation-and-prefixing.test.ts
Outdated
Show resolved
Hide resolved
… into sass-embedded
@timneutkens all tests pass except the new flakes. The tests do not fail, but the 2nd run does not complete within the max. minutes the runner has. See https://github.com/vercel/next.js/actions/runs/9515680178/job/26230449914?pr=64577 and https://github.com/vercel/next.js/actions/runs/9515680178/job/26230451465?pr=64577 What to do here? |
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 good to land now, checked with @ztanner and the failure on the flaky check happens when too many tests are changed
Next step: update branch and merge? |
What?
This PR adds an option to use
sass-embedded
.Why?
For large projects sass-embedded improves SCSS compilation time by over 50%.
See also #36160
How?
Added a sassOption
implementation
to configure the sass-loader which Sass implementation to use.See also https://www.npmjs.com/package/sass-loader#implementation
I think this a similar approach to what is done for
additionalData
.Additional notes
In order to support
sass-embedded
,sass-loader
is upgraded to 12.6.0.