Skip to content
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

The requested module '/_nuxt/@fs/=/node_modules/.cache/vite/client/deps/@intlify_shared.js' does not provide an export named 'assign' #2098

Closed
mateusk opened this issue May 22, 2023 · 10 comments · Fixed by intlify/eslint-plugin-vue-i18n#382 or #2239
Labels
deps 🍰 p2-nice-to-have Priority 2: nothing is broken but it's worth addressing upstream issue v8 WIP workaround

Comments

@mateusk
Copy link

mateusk commented May 22, 2023

Environment

------------------------------
- Operating System: Darwin
- Node Version:     v16.19.1
- Nuxt Version:     3.4.2
- Nitro Version:    2.4.1
- Package Manager:  [email protected]
- Builder:          vite
- User Config:      srcDir, css, runtimeConfig, typescript, modules, imports, i18n, vite, app
- Runtime Modules:  @nuxtjs/[email protected], @vueuse/[email protected], [email protected], @pinia/[email protected]
- Build Modules:    -
------------------------------

Reproduction

Cannot reproduce this in a new Nuxt project, sorry.

Describe the bug

Uncaught SyntaxError: The requested module '/_nuxt/@fs/app/node_modules/.cache/vite/client/deps/@intlify_shared.js?v=85d61870' does not provide an export named 'assign' (at message-compiler.mjs?v=27c99670:6:18)

My Nuxt app was running fine until this strange error came up all of a sudden. Could not replicate this issue in a new Nuxt 3 project, so I cannot provide a reproduction repo, sorry. Tried downgrading @nuxtjs/i18n, same. Tried removing /node_modules, reinstalling dependencies, same.

Thanks in advance for any clues.

Additional context

No response

Logs

No response

@mateusk
Copy link
Author

mateusk commented May 22, 2023

Turns out I had @intlify/eslint-plugin-vue-i18n which also depends on @intlify/message-compiler but installs a different version, and that was generating a conflict. Uninstalled @intlify/eslint-plugin-vue-i18n and all works again.

@dargmuesli
Copy link
Collaborator

Let's keep this open to further track the issue if that's fine for you, @mateusk. It might not be the perfect solution for everyone to just uninstall their linter plugin. A beta release for @intlify/eslint-plugin-vue-i18n seems to be needed.

@dargmuesli dargmuesli reopened this May 29, 2023
@dargmuesli dargmuesli added dependencies Pull requests that update a dependency file upstream issue v8 🍰 p2-nice-to-have Priority 2: nothing is broken but it's worth addressing workaround WIP and removed pending triage dependencies Pull requests that update a dependency file labels May 29, 2023
@dargmuesli
Copy link
Collaborator

See intlify/eslint-plugin-vue-i18n#373 as my WIP which could be released in a beta version as suggested.

@mathieuCatapulpe
Copy link

In case this might help someone, I faced a simular issue as explained in #2110 and managed to fix it by using yarn instead of npm

@valernyx
Copy link

valernyx commented Jun 8, 2023

We are having this same issue as well (same error message), but our repo is not using the eslint-plugin-vue-i18n. We have other eslint plugins however, so I'm trying to determine if it's related to one of them. No luck getting it running so far :(

@dargmuesli
Copy link
Collaborator

Check why @intlify/shared is used, e.g. by pnpm why @intlify/shared, and why there are most likely different versions in use compared to your other intlify dependencies.

@valernyx
Copy link

valernyx commented Jun 8, 2023

Check why @intlify/shared is used, e.g. by pnpm why @intlify/shared, and why there are most likely different versions in use compared to your other intlify dependencies.

@dargmuesli Thank you! We have @intlify/shared used as a dep for a few other packages and it was using version 9.2.2 for them. I was able to resolve the issue by adding the following to our package.json:

"overrides": {
    "@intlify/shared": "9.3.0-beta.17"
},

Appreciate the quick assistance! 🎉

@ghost
Copy link

ghost commented Jun 15, 2023

Check why @intlify/shared is used, e.g. by pnpm why @intlify/shared, and why there are most likely different versions in use compared to your other intlify dependencies.

I use @nuxtjs/i18n in the project and I get an error with @intlify_shared, I tried the above actions, nothing helped, how else can I solve this problem?

@dargmuesli
Copy link
Collaborator

You could wait for the merge and release of intlify/eslint-plugin-vue-i18n#382 if you use @intlify/eslint-plugin-vue-i18n.

@ghost
Copy link

ghost commented Jun 16, 2023

You could wait for the merge and release of intlify/eslint-plugin-vue-i18n#382 if you use @intlify/eslint-plugin-vue-i18n.

So I don't use @intlify/eslint-plugin-vue-i18n, but the error is still present

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deps 🍰 p2-nice-to-have Priority 2: nothing is broken but it's worth addressing upstream issue v8 WIP workaround
Projects
None yet
5 participants