Nuxt•2y ago

Linked ESM package not found

I am trying to import from a linked package that I've built with vite (in library mode). When I try to run the dev script, I get:

Failed to load url /@fs/Users/david.marr/code/ui-components/packages/Utils/lib/index.mjs (resolved id: /Users/david.marr/code/ui-components/packages/Utils/lib/index.mjs) in /Users/david.marr/code/app/src/plugins/filters.js. Does the file exist?

I don't have type: 'module' in either the app or the package i'm trying to import. I've linked the package and verified that it is in node_modules. Not sure what the issue is... If I run the build script, the issue doesn't appear. I also am able to import this package in a fresh nuxt 3 app, so maybe there is something with linking that is the issue?

18 Replies

dmarrOP•2y ago

seems like i'm required to use .ts extension and lang="ts" in my vue files well removing my old jsconfig.json seems to get past that, but now I get the same error on a vue file

Unknown User•2y ago

Message Not Public

dmarrOP•2y ago

so in package's package.json:

  "main": "index.js",
  "module": "lib/index.mjs",
  "type": "module",

  "main": "index.js",
  "module": "lib/index.mjs",
  "type": "module",

in the lib/ dir, the index.mjs file is present would having a jsconfig.json file impact anything? I'm trying to narrow down why a clean nuxt3 project can import just fine, but my nuxt2->nuxt3 upgrade cannot appears I need to add to vite config in nuxt.config.js:

vite: {
    optimizeDeps: {
      include: ['my-linked-package']
    },
}

vite: {
    optimizeDeps: {
      include: ['my-linked-package']
    },
}

dmarrOP•2y ago

https://vitejs.dev/config/dep-optimization-options.html#optimizedeps-include

Vite

Next Generation Frontend Tooling

Unknown User•2y ago

Message Not Public

dmarrOP•2y ago

yeah i tried both. i think something about the package being linked was causing issues

Unknown User•2y ago

Message Not Public

dmarrOP•2y ago

Hi, I havent found a solution. I ended up starting a new monorepo and I'm moving things over 😦

Unknown User•2y ago

Message Not Public

dmarrOP•2y ago

ok thanks. I was playing around with the vite section of nuxt config.

vite: {
    optimizeDeps: {
      include: [
        'my-linked-repo',
      ]
    }
}

vite: {
    optimizeDeps: {
      include: [
        'my-linked-repo',
      ]
    }
}

i don't know why but it seemed to get past some errors, but something with the way my external package (using vite lib mode) was built that nuxt didn't like the other crappy workaround was npm pack in the external package and installing from that

Unknown User•2y ago

Message Not Public

🇨🇭 Marko Bolliger <cannap>•2y ago

maybe transpile it

Unknown User•2y ago

Message Not Public

dmarrOP•2y ago

Thank you @Nobsow -- good work! I will give it a try today

Unknown User•2y ago

Message Not Public

dmarrOP•2y ago

Cheers, that seems to have gotten past that issue. I have more problems now ,but maybe cjs related: Cannot access 'renderer$1' before initialization

dmarrOP•2y ago

There is a recent report of it happening to someone else https://github.com/nuxt/nuxt/issues/20576#issuecomment-1528855705

GitHub

Cannot access 'renderer$1' before initialization is:closed · Issue...

Environment Operating System: Darwin Node Version: v18.12.1 Nuxt Version: 3.4.3 Nitro Version: 2.3.3 Package Manager: [email protected] Builder: vite User Config: ssr, app, css, modules, schemaOrg, windi...

dmarrOP•2y ago

this ended up being an issue with a server api route.

Gaming

Programming

Linked ESM package not found