This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Docs: how to opt back into SWC #36590
Labels
Documentation
Related to Next.js' official documentation.
Comments
JoshuaKGoldberg
added
the
Documentation
kodiakhq bot
pushed a commit
that referenced
this issue
May 10, 2022
fixes #36763 fixes #36590 ## Feature - [x] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - It hasn't been accepted for implementation, although that process isn't clear, and this is a pretty trivial fix. - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [x] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - This is somewhat inherent in the error log - [x] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [x] Make sure the linting passes by running `yarn lint`
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
What is the improvement or update you wish to see?
https://nextjs.org/docs/messages/swc-disabled explains why a project opted out of SWC, but doesn't explain how to explicitly opt in. Is that possible? (if not, I suppose this is a feature request)
Is there any context that might help us understand?
Other tools such as Jest and Storybook react to the presense of a
.babelrc. It's inconvenient -or sometimes not supported well- to have to configure those tools to point to a custom.babelrclocation.Does the docs page already exist? Please link to it.
https://nextjs.org/docs/messages/swc-disabled
The text was updated successfully, but these errors were encountered: