-
Notifications
You must be signed in to change notification settings - Fork 186
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
FATAL No "exports" main defined in unicorn-magic\package.json #954
Comments
same thing. Locking module to specific version worked for me: "@nuxtjs/tailwindcss": "6.11.4" |
Are you using Nuxt 2? I think I'll need a reproduction please 🙏 |
Yes, in Nuxt2 |
I am also seeing this error when using "@nuxtjs/tailwindcss": "6.13.2", Pre-transform error: [postcss] No "exports" main defined in xxxx/node_modules/unicorn-magic/package.json but it doesn't happen in 6.13.1 or below |
Same issue when trying to use |
OK - I've oddly hit the same issue in my Nuxt 3 project now. Let me investigate 👍 |
Some related issues: nuxt/vercel-builder#850, sindresorhus/globby#260 Unfortunately I can't quite fix this within the module scope, it is likely to be an upstream issue somewhere ( I can ask you to pin |
Environment
in dev and prod
Reproduction
No response
Describe the bug
the problem just from yesterday , , It was work in last year , but now i get this error
╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ ✖ Nuxt Fatal Error │
│ │
│ Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in node_modules\unicorn-magic\package.json │
│ │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
i search where this package used , it's in this package used
"dependencies": {
"@nuxt/kit": "^3.13.2",
and @nuxt/kit use
"globby": "^14.0.2",
and globby use "unicorn-magic": "^0.1.0"
after i remove @nuxtjs/tailwindcss from modules
modules: [
npm run dev work again
Additional context
No response
Logs
The text was updated successfully, but these errors were encountered: