Weird issues after upgrading to version 1.0

[thomashohn]

Hi

After upgrading to version 1.0.0 and following the guide - we have started to see this error in a project that uses a shared component

[ nuxi  12:01:24 PM]  ERROR  Cannot start nuxt:  Error while importing module @gyldendalsolutions/sharedcomponents: Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/Volumes/dev/repos/my_ibooks_frontend/node_modules/.pnpm/jiti@2.4.2/node_modules/jiti/node_modules/.pnpm/jiti@2.4.2/node_modules/jiti/lib/jiti.mjs' imported from /Volumes/dev/repos/my_ibooks_frontend/node_modules/.pnpm/jiti@2.4.2/node_modules/jiti/lib/jiti.mjs
    at loadNuxtModuleInstance (node_modules/.pnpm/@nuxt+kit@3.16.2_magicast@0.3.5/node_modules/@nuxt/kit/dist/index.mjs:2565:15)
    at async installModule (node_modules/.pnpm/@nuxt+kit@3.16.2_magicast@0.3.5/node_modules/@nuxt/kit/dist/index.mjs:2480:67)
    at async initNuxt (node_modules/.pnpm/nuxt@3.16.2_@parcel+watcher@2.5.1_@types+node@22.14.0_db0@0.3.1_eslint@9.24.0_jiti@2.4._0bcfd39a16c7773726dbc85ef80643ae/node_modules/nuxt/dist/shared/nuxt.iYoBCR2R.mjs:5833:5)
    at async NuxtDevServer._load (node_modules/.pnpm/@nuxt+cli@3.24.1_magicast@0.3.5/node_modules/@nuxt/cli/dist/chunks/dev2.mjs:183:5)
    at async NuxtDevServer.load (node_modules/.pnpm/@nuxt+cli@3.24.1_magicast@0.3.5/node_modules/@nuxt/cli/dist/chunks/dev2.mjs:111:7)
    at async NuxtDevServer.init (node_modules/.pnpm/@nuxt+cli@3.24.1_magicast@0.3.5/node_modules/@nuxt/cli/dist/chunks/dev2.mjs:106:5)
    at async Object.run (node_modules/.pnpm/@nuxt+cli@3.24.1_magicast@0.3.5/node_modules/@nuxt/cli/dist/chunks/dev-child.mjs:95:5)
    at async runCommand (node_modules/.pnpm/citty@0.1.6/node_modules/citty/dist/index.mjs:316:16)
    at async runCommand (node_modules/.pnpm/citty@0.1.6/node_modules/citty/dist/index.mjs:307:11)
    at async runMain (node_modules/.pnpm/citty@0.1.6/node_modules/citty/dist/index.mjs:445:7)

The componets works fine with 0.8.4 - but is included via
 "@gyldendalsolutions/sharedcomponents": "file:../sharedcomponents",

Could that cause an issue with the latest version?

[github-actions]

We cannot recreate the issue with the provided information. Please add a reproduction in order for us to be able to investigate.

Why was this issue marked with the needs-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. Please provide a link to either :

• a public GitHub repository
• a CodeSandbox
• a StackBlitz.

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

What happens if I don't provide a sufficient minimal reproduction?

Issues with the needs-reproduction label that receives no meaningful activity (e.g. new comments with a reproduction link) will be closed by the maintainers and won't be looked at.

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps. Furthermore, you can upvote the issue using a reaction on the topmost comment.

• Please do not comment "I have the same issue" without repro steps
• Please do not comment un-helpful messages such as "+1" on an issue, use reactions on the first comment instead.

I think my reproduction is good enough, why aren't you looking into it quicker?

We constantly monitor open issues for new comments.

However, sometimes we might miss one or two. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible.

I have a minimal reproduction to contribute to a closed issue.

If you have a minimal reproduction for a closed issue, please write a comment on the issue with a link to the reproduction.
We will review it and reopen the issue if it is sufficient.

Useful Resources

• Why reproductions are required
• How to create a Minimal, Complete, and Verifiable example