Replies: 2 comments 2 replies
-
Just a fyi with regards to the Next 12 + swc issues issues, vercel/next.js#48593 seems to be where this was discussed at length. Unfortunately the bulk of the discussion seems centered around the issues with Next 13, haven't tried the overrides solution applies here. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Having the same issue. Not running Nextjs. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone
Our design system is shipped via a monorepo implemented with yarn workspaces and we publish the React components to a private npm registry. That library includes a folder with a simple app that we use to check for type augmentations with
skipLibCheck: true
in itstsconfig.json
file.For context:
react-aria-components
@types/react
, for example/releases
that calls NextJS 12 a dependency, and that depends on the components library, which we instruct to depend on using@our-lib/react: "*"
.Yesterday we started noticing that
tsc --noEmit
displays these errors:So one of the monorepo packages is including some React types that
react-aria
doesn't like, and I'm trying to run them down now.Additionally, the builds for the Next 12 project fail with the same failures that @LFDanLu observed here:
I understand that it's hard to opine without a repro, but can anyone make a recommendation for how they might tackle this?
Beta Was this translation helpful? Give feedback.
All reactions