-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Babel TypeScript transformer does not support satisfies operator #43799
Comments
Any news? |
The problem seems discussed in babel/babel#15157. |
any news how to fix? |
@domosedov Is it solved? Could you reopen if not? |
I upgraded and ensured all of our @babel/* dependencies were deduplicated and on the proper versions, and I still was unable to get this to work with Next's Babel setup. I didn't have time to dig into it more, but it seems like the issue might be with the I ultimately realized I really didn't need the customizations our Babel configuration provided, and I ended up upgrading to Next.js 13.2.1 and removed our Babel configuration to switch to the SWC compiler. Everything is working great with that setup. If you're looking to do the same, keep in mind that you'll need to be on Next.js 13+ ( |
@ jrolfs Unfortunately, I can't get rid of Babel as easily as you can. |
did anyone manage to solve this? 🙏 |
Verсel seems to have no respect for users who still use the pages approach with babel configuration. 👎 |
Well this sucks |
|
Any updates on this issue? @domosedov were you able to find any workaround? |
No |
any updates on this? afaik Next maintainers just need to bump babel and this would work... |
I'd like to know how to speed up this process. |
### What? Update Babel packages across the board ### Why? Since you ship vendored presets and plugins it's impossible for people to update this stuff at their own pace - independently from Next. So users of `next/babel` are currently stuck with old versions and, for example, they might not be able to use the TS `satisfies` operator. ### How? I just updated ranges (to pinned ones) where I could find them, run `corepack pnpm i` and re-run build scripts in the `packages/next`. Fixes #43799
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. |
Verify canary release
Provide environment information
Operating System:
Platform: linux
Arch: x64
Version: Ubuntu 20.04.0 LTS Wed Dec 07 2022 11:10:08 GMT+0300 (Москва, стандартное время)
Binaries:
Node: 16.14.2
npm: 7.17.0
Yarn: 1.22.19
pnpm: 7.13.6
Relevant packages:
next: 13.0.7-canary.1
eslint-config-next: N/A
react: 18.2.0
react-dom: 18.2.0
Which area(s) of Next.js are affected? (leave empty if unsure)
No response
Link to the code that reproduces this issue
https://stackblitz.com/edit/vercel-next-js-pa3kjy?file=pages%2Findex.tsx
To Reproduce
npm run dev
Describe the Bug
Expected Behavior
No error
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
The text was updated successfully, but these errors were encountered: