Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

vite: module does not provide an export named 'i18nVue'

See original GitHub issue

Also: after upgrade from 0.2.1 to 0.4.1:

Uncaught SyntaxError: The requested module '/node_modules/.vite/laravel-vue-i18n.js?v=4bc78461' does not provide an export named 'i18nVue'

This happened with v3 also, rolling back to 0.2.1 it works again.

_Originally posted by @ibrunotome in https://github.com/xiCO2k/laravel-vue-i18n/issues/3#issuecomment-1008974849_

Issue Analytics

State:
Created 2 years ago
Comments:10 (6 by maintainers)

Top GitHub Comments

1reaction

xiCO2kcommented, Jan 12, 2022

yes the problem was the change to compile with “node12”

{
  "compilerOptions": {
    "target": "es2015",
    "module": "node12",
    "outDir": "dist",
    "sourceMap": true,
    "declaration": true,
    "allowSyntheticDefaultImports": true,
    "esModuleInterop": true,
    "skipDefaultLibCheck": true
  },
  "files": [
    "./node_modules/@types/node/index.d.ts"
  ],
  "include": [
    "src/**/*.ts"
  ],
  "exclude": [
    "node_modules"
  ],
  "rules": {
    "no-console": false
  }
}

That’s needed to have the defaultResolver with the import (introduced in v0.3.0).

Trying to find a way to have it working well with vite and webpack.

Will keep you posted.

0reactions

xiCO2kcommented, Jan 19, 2022

Awesome!