-
-
Notifications
You must be signed in to change notification settings - Fork 144
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
TS issue importing from clsx/lite #89
Comments
Hmm… clear cache maybe? Perhaps where you’re writing this is resolving to an older version? Eg clsx@2.0 within a workspace |
It was on a project which did not have a prior version of |
Oh. Play with your tsconfig settings for module/moduleResolution. Only certain combos respect the exports map |
Changing |
Switching to |
Closing as this is a TypeScript ( |
Changing the moduleResolution is not an option when using nextjs.
The value get's set back to node when changed to "Bundler" |
Gotta love it... In such case @VinitSarvade, you can/should just use If you really want to use |
Thank you for the explanation @lukeed. I like the idea of path alias, but like you mentioned the difference is not really much. The larger goal was mostly to ensure a uniform string arguments only option. |
Excited to try out the new
lite
approach:But I'm running into a TypeScript import error:
Is there something I'm doing wrong? Installed
clsx 2.1.0
viapnpm 8.12.1
The text was updated successfully, but these errors were encountered: