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
Nuxt 3.9.0 Internal server error: Soft-invalidated module "entry.js" should not have existing transform result #3472
Comments
… critters unocss/unocss#3472 when the issue is solve we must remove the inlineStyles: false on nuxt.config.ts
update: after testing with the latest unocss (0.58.3), this issue is still not solved |
I do indeed have the same issue but it kinda disappears after a few refreshes? Not really consistent but not a huge blocker either. 🤔 |
+1, I have temporarily downgraded nuxt to version 3.8.2. |
+1, having the same issue. |
Also having this issue
But this does seem to do the trick as-well no issues with my build and deployments! But big red internal server error sends gives me chills 🙃 |
Working with Netlify Edge functions locally is not always perfect (works fine on an M3 chip but less on a Linux machine for some reason) but still achievable, just need to guess that the server crashes before the functions are called and restart Netlify CLI. |
After upgrading to Nuxt 3.9.3 everything is working fine for me. |
unocss 5.8.3 |
Any news on this? |
@antfu any updates? The error is sometimes so intrusive that it is impossible to work. Sometimes, 1-2 page refreshes helps, but sometimes 40 refreshes still with error |
Putting this in my Nuxt config worked in my scenario: export default defineConfig({
features: {
inlineStyles: false,
},
}) |
The error still appears despite this |
Welp, somehow it did fix it in my specific scenario. I'm using the latest version of Nuxt if that helps. |
I can't reproduce with @serkodev's reproduction with the latest versions anymore. Can anyone provide another minimal reproductions? |
+1, having the same issue. |
Again, I would need a minimal reproduction to investigate this - saying +1 does not improve the situation, for the record. Thanks |
Under my test, I need to open F12, disable network cache, it only seems to appear on the second load, if the cache is not disabled, then it will not load the second time For replication code, just nuxt+unocss After some testing, it seems to be caused by |
I'm not coding nuxt, but I tried debug error after I read on Twitter =))) Step: |
Do you please have the link for your code? A video record is not considered a valid reproduction unfortunately. 😅 |
I downloaded code from stackblitz. link above |
https://stackblitz.com/edit/github-dqvhqs?file=package.json
|
I have the same issue: nuxt: 3.9.3 uno presets: [
presetUno(),
presetForms(),
presetHeadlessUi(),
presetIcons(),
presetAttributify(),
presetScrollbar(),
presetWebFonts({
provider: 'google',
fonts: {
sans: {
name: 'Roboto',
weights: [400, 500, 700],
},
},
}),
] When I start the local server with the script: When I reinstall everything, including cleaning the pnpm lock file, the server becomes stable and error-free until I restart the PC. |
You can use any one reproduction from above and test it like just refresh the page in browser. I think its not working on stackblitz or any sandboxes, you need start it on local environment |
|
Maybe it is also depending on the OS of the user. In my case Linux (Ubuntu) works worse than MacOS hence it's a bit tricky to reproduce properly on MacOS. |
Already update the reproduction link with the latest UnoCSS version
Steps
reproduction.mov |
It's probably introduced in vitejs/vite#14654, not yet sure how to fix it, investigating |
Alright, hopefully vitejs/vite#15768 should fix this |
Just tested and this issue should be fixed since |
UnoCSS version
0.58.2
Describe the bug
After running nuxt dev server, go to browser and refresh the page once, the error will show up.
Reproduction
@unocss/nuxt
modulenuxt dev
https://stackblitz.com/edit/github-xtxzaj?file=package.json
Additional info
Already try to add the following config regarding to #3468 (comment) but still having error
System Info
Validations
The text was updated successfully, but these errors were encountered: