-
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
SWC does not catch nested styled-jsx
tags in props
#65064
Labels
bug
Issue was opened via the bug report template.
linear: next
Confirmed issue that is tracked by the Next.js team.
locked
SWC
Related to minification/transpilation in Next.js.
Comments
github-actions
bot
added
the
SWC
Related to minification/transpilation in Next.js.
label
Apr 25, 2024
Just to have the code on this page as well:
|
samcx
added
the
linear: next
Confirmed issue that is tracked by the Next.js team.
label
Apr 26, 2024
swc-project/plugins#292 should fix this issue. I'll close this issue with a PR to update |
kdy1
added a commit
to vercel/turborepo
that referenced
this issue
May 17, 2024
### Description - Closes PACK-3042 - Closes NEXT-3241 - Closes NEXT-3242 - Closes vercel/next.js#46887 - Closes vercel/next.js#65064 - Closes vercel/next.js#65066 - Closes vercel/next.js#65237 ### Testing Instructions See [next.js counterpart](vercel/next.js#65450)
This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Neosoulink
pushed a commit
to Neosoulink/turbo
that referenced
this issue
Jun 14, 2024
### Description - Closes PACK-3042 - Closes NEXT-3241 - Closes NEXT-3242 - Closes vercel/next.js#46887 - Closes vercel/next.js#65064 - Closes vercel/next.js#65066 - Closes vercel/next.js#65237 ### Testing Instructions See [next.js counterpart](vercel/next.js#65450)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bug
Issue was opened via the bug report template.
linear: next
Confirmed issue that is tracked by the Next.js team.
locked
SWC
Related to minification/transpilation in Next.js.
Link to the code that reproduces this issue
https://github.com/sjchmiela/swc-style-in-prop-bug
To Reproduce
npm run dev
,yarn dev
, whichever you prefer).true
for a non-boolean attributejsx
.")Current vs. Expected behavior
I expected a "Nesting detected" error to be thrown. It is thrown if SWC is disabled and Babel is transpiling styles.
Provide environment information
Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 22.6.0: Wed Jul 5 22:22:52 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T8103 Available memory (MB): 16384 Available CPU cores: 8 Binaries: Node: 18.19.0 npm: 10.2.3 Yarn: 1.22.21 pnpm: 9.0.1 Relevant Packages: next: 14.3.0-canary.23 // Latest available version is detected (14.3.0-canary.23). eslint-config-next: N/A react: 18.3.0 react-dom: 18.3.0 typescript: 5.1.3 Next.js Config: output: N/A
Which area(s) are affected? (Select all that apply)
SWC
Which stage(s) are affected? (Select all that apply)
next dev (local), next build (local), next start (local)
Additional context
It affects all stages, because without the error about nested styles untranspiled CSS ends up being served to clients.
NEXT-3242
The text was updated successfully, but these errors were encountered: