-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
refactor(turbopack-ecmascript): deprecate enable_emotion, enable_styled* #4955
Merged
Conversation
This file contains 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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Ignored Deployments
|
✅ This change can build |
|
kwonoj
force-pushed
the
deprecate-3rdparty-transform
branch
2 times, most recently
from
May 16, 2023 18:29
4f7e140
to
cebf4d1
Compare
Linux Benchmark for c0283af
Click to view full benchmark
|
MacOS Benchmark for c0283af
Click to view full benchmark
|
kwonoj
force-pushed
the
deprecate-3rdparty-transform
branch
from
May 16, 2023 21:37
cebf4d1
to
8b2aed7
Compare
Linux Benchmark for 9fa4a80
Click to view full benchmark
|
MacOS Benchmark for 9fa4a80
Click to view full benchmark
|
kwonoj
force-pushed
the
deprecate-3rdparty-transform
branch
from
May 22, 2023 16:45
8b2aed7
to
9d81d7c
Compare
Linux Benchmark for 6291a68Click to view benchmark
|
jridgewell
approved these changes
May 22, 2023
MacOS Benchmark for 6291a68
Click to view full benchmark
|
kwonoj
added
the
pr: automerge
Kodiak will merge these automatically after checks pass
label
May 22, 2023
sokra
added a commit
to vercel/next.js
that referenced
this pull request
May 23, 2023
### What? * allow to apply existing pipeline * change webpack loader key to glob for more flexibility * add test cases * add special error message when using the old config syntax Old config: ```js experimental: { turbo: { loaders: { ".mdx": ["mdx-loader"] } } } ``` New config ``` js experimental: { turbo: { rules: { // key is a glob now // normal syntax will treat the result as ecmascript code "*.mdx": ["mdx-loader"], // glob allows more advanced matching "./images/**/*.png": { loaders: ["image-optimize-loader"], // result of loader will be handled in other steps // under the same name/path (here .png) // This will use the existing .png pipeline (static asset) // It might also use other rules matching .png. as: "*" }, "*.generate-image.js": { loaders: ["image-generation-loader"], // It also possible to pass this under a different name // into the pipeline. Here it will treat the result as png image as: "*.png" } } } } ``` ### Why? More flexibility and allowing to use the builtin module handling over non-js types. fixes WEB-1009 ### Turbopack changes * vercel/turborepo#4955 <!-- OJ Kwon - refactor(turbopack-ecmascript): deprecate enable_emotion, enable_styled* --> * vercel/turborepo#4880 <!-- Tobias Koppers - refactor webpack loader execution --> --------- Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
hydRAnger
pushed a commit
to hydRAnger/next.js
that referenced
this pull request
Jun 12, 2023
### What? * allow to apply existing pipeline * change webpack loader key to glob for more flexibility * add test cases * add special error message when using the old config syntax Old config: ```js experimental: { turbo: { loaders: { ".mdx": ["mdx-loader"] } } } ``` New config ``` js experimental: { turbo: { rules: { // key is a glob now // normal syntax will treat the result as ecmascript code "*.mdx": ["mdx-loader"], // glob allows more advanced matching "./images/**/*.png": { loaders: ["image-optimize-loader"], // result of loader will be handled in other steps // under the same name/path (here .png) // This will use the existing .png pipeline (static asset) // It might also use other rules matching .png. as: "*" }, "*.generate-image.js": { loaders: ["image-generation-loader"], // It also possible to pass this under a different name // into the pipeline. Here it will treat the result as png image as: "*.png" } } } } ``` ### Why? More flexibility and allowing to use the builtin module handling over non-js types. fixes WEB-1009 ### Turbopack changes * vercel/turborepo#4955 <!-- OJ Kwon - refactor(turbopack-ecmascript): deprecate enable_emotion, enable_styled* --> * vercel/turborepo#4880 <!-- Tobias Koppers - refactor webpack loader execution --> --------- Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 25, 2024
…ed* (vercel/turborepo#4955) ### Description WEB-1048. With #49621, now we can consolidate most of non-core transforms into ecmaplugins. Postcss / mdx are the only exceptions, but not immediate priority compare to work (which requires to setup some rules instead of just plugins) and filed 1054/1055 for those to deal with later.
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 29, 2024
…ed* (vercel/turborepo#4955) ### Description WEB-1048. With #49621, now we can consolidate most of non-core transforms into ecmaplugins. Postcss / mdx are the only exceptions, but not immediate priority compare to work (which requires to setup some rules instead of just plugins) and filed 1054/1055 for those to deal with later.
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Aug 1, 2024
…ed* (vercel/turborepo#4955) ### Description WEB-1048. With #49621, now we can consolidate most of non-core transforms into ecmaplugins. Postcss / mdx are the only exceptions, but not immediate priority compare to work (which requires to setup some rules instead of just plugins) and filed 1054/1055 for those to deal with later.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
WEB-1048.
With vercel/next.js#49621, now we can consolidate most of non-core transforms into ecmaplugins.
Postcss / mdx are the only exceptions, but not immediate priority compare to work (which requires to setup some rules instead of just plugins) and filed 1054/1055 for those to deal with later.