-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Rollup failed to resolve import "vue/server-renderer" #3035
Comments
This looks like it's related to #2187 |
I tried forking your repo but can't get the actions running. moon was panicking. Most likely you're hitting a weird edge case. I am seeing similar issues on Nuxt side too. Can you try something along the lines of: // .vitepress/config.ts
vite: {
resolve: {
alias: {
'vue/server-renderer': require.resolve('vue/server-renderer/index.mjs'),
}
}
} |
@brc-dd will be giving that solution a try tomorrow |
Getting this error in CI, but not locally. Could it be tied to npm workspaces? Locally running on Mac M1. |
@boyum Can you check if the above workaround works? 👀 |
Thanks for the quick response! The above (using import.meta.resolve) breaks the build locally, but I haven't yet tried in CI. |
vite: {
resolve: {
alias: {
"vue/server-renderer": import.meta.resolve(
"vue/server-renderer/index.mjs",
),
},
},
} produces:
|
vite: {
resolve: {
alias: {
"vue/server-renderer": import.meta.resolve(
"vue/server-renderer",
),
},
},
} produces:
|
The same happens in CI (https://github.com/boyum/markdown-it-image-size/actions/runs/12507674626/job/34894568029?pr=762). |
Hmm. I've got no idea then. It most likely has something to do with turbo in your case. |
I wonder if it has something to do with the Mx processors and how npm installs packages? I made it work by copying a previous package-lock file and doing a new install. boyum/markdown-it-image-size@7bba314 |
Describe the bug
Just as reported with #2713, I'm running into an error of:
Rollup failed to resolve import "vue/server-renderer"
. The error happens during execution ofvitepress build
and apparently only on CI.Reproduction
Link to the failing workflow: https://github.com/shellscape/jsx-email/actions/runs/6365095364/job/17281850884#step:12:104
Link to the site's source: https://github.com/shellscape/jsx-email/tree/main/apps/web.
Link to the workflow: https://github.com/shellscape/jsx-email/blob/main/.github/workflows/release.yml
To reiterate: This does not happen locally on my Mac M2 Ventura, it only occurs in CI
Expected behavior
I would have expected no build error. This looks like an environment specific issue.
System Info
Additional context
No response
Validations
Update:
npm info virepress version
must have been cached or something on my end because it was resolving rc17 earlier. looked it up manually and updated to vitepress v1.0.0-rc.20 and no difference on CI. Failing workflow with rc20 can be viewed here: https://github.com/shellscape/jsx-email/actions/runs/6365219441/job/17282058140#step:12:101The text was updated successfully, but these errors were encountered: