-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
[Bug Report] 5.2.12 regression - dynamic css import will cause MODULE_NOT_FOUND in SSR build #17366
Closed
7 tasks done
Labels
feat: css
feat: ssr
p3-minor-bug
An edge case that only affects very specific usage (priority)
regression
The issue only appears after a new release
Comments
Maybe related #16078 |
Yes that's it. It's a regression that breaks some vuepress plugins during SSR. cc @sapphi-red |
nekomeowww
added a commit
to nolebase/integrations
that referenced
this issue
Jun 3, 2024
…l0sNRNKZ.js Cannot find module '/Users/neko/Git/nolebase/integrations/docs/.vitepress/.temp/style.l0sNRNKZ.js' imported from /Users/neko/Git/nolebase/integrations/docs/.vitepress/.temp/app.js Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/Users/neko/Git/nolebase/integrations/docs/.vitepress/.temp/style.l0sNRNKZ.js' imported from /Users/neko/Git/nolebase/integrations/docs/.vitepress/.temp/app.js Already fixing: [Bug Report] 5.2.12 regression - dynamic css import will cause MODULE_NOT_FOUND in SSR build · Issue #17366 · vitejs/vite vitejs/vite#17366 Signed-off-by: Neko Ayaka <neko@ayaka.moe>
nekomeowww
added a commit
to nolebase/integrations
that referenced
this issue
Jun 3, 2024
…l0sNRNKZ.js Cannot find module '/Users/neko/Git/nolebase/integrations/docs/.vitepress/.temp/style.l0sNRNKZ.js' imported from /Users/neko/Git/nolebase/integrations/docs/.vitepress/.temp/app.js Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/Users/neko/Git/nolebase/integrations/docs/.vitepress/.temp/style.l0sNRNKZ.js' imported from /Users/neko/Git/nolebase/integrations/docs/.vitepress/.temp/app.js Already fixing: [Bug Report] 5.2.12 regression - dynamic css import will cause MODULE_NOT_FOUND in SSR build · Issue #17366 · vitejs/vite vitejs/vite#17366 Signed-off-by: Neko Ayaka <neko@ayaka.moe>
nekomeowww
added a commit
to nolebase/integrations
that referenced
this issue
Jun 5, 2024
…dalone packages (#229) * fix: build error Error [ERR_MODULE_NOT_FOUND] .vitepress/.temp/style.l0sNRNKZ.js Cannot find module '/Users/neko/Git/nolebase/integrations/docs/.vitepress/.temp/style.l0sNRNKZ.js' imported from /Users/neko/Git/nolebase/integrations/docs/.vitepress/.temp/app.js Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/Users/neko/Git/nolebase/integrations/docs/.vitepress/.temp/style.l0sNRNKZ.js' imported from /Users/neko/Git/nolebase/integrations/docs/.vitepress/.temp/app.js Already fixing under [[Bug Report] 5.2.12 regression - dynamic css import will cause MODULE_NOT_FOUND in SSR build · Issue #17366 · vitejs/vite](vitejs/vite#17366) * chore: update to main * chore: correct package.json Signed-off-by: Neko Ayaka <neko@ayaka.moe>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
feat: css
feat: ssr
p3-minor-bug
An edge case that only affects very specific usage (priority)
regression
The issue only appears after a new release
Describe the bug
Dynamic import css file:
![image](https://private-user-images.githubusercontent.com/18205362/335633357-24929117-0960-4c71-a8cf-aa5084716f3d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjEzNzk2MjMsIm5iZiI6MTcyMTM3OTMyMywicGF0aCI6Ii8xODIwNTM2Mi8zMzU2MzMzNTctMjQ5MjkxMTctMDk2MC00YzcxLWE4Y2YtYWE1MDg0NzE2ZjNkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzE5VDA4NTUyM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTI0ZjkzMDhhMWIxYzdjZjdjM2ZiYzZjMGFlNzBlYjFjMTU4YmQ0OWM2NGFjMzhkNGQyNzQxMzU1NGVhM2I3NmMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.wUb5cGIL_HYf7Z5gc3fFD57SVKoHLrs9sEl95xtPNwU)
SSR build in 5.2.11:
![image](https://private-user-images.githubusercontent.com/18205362/335633666-c3c1ba6e-4515-4d0a-8fc8-989e041c6fab.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjEzNzk2MjMsIm5iZiI6MTcyMTM3OTMyMywicGF0aCI6Ii8xODIwNTM2Mi8zMzU2MzM2NjYtYzNjMWJhNmUtNDUxNS00ZDBhLThmYzgtOTg5ZTA0MWM2ZmFiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzE5VDA4NTUyM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTRlMzJhY2UwZjc1MWMxMzM5MDA4NjJmNDZlZTc4YmJkZTYyMjFlOWQxY2IyM2E3NTNkNTcwYWU3NDMyNzhkNTcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.giuPaNK_GxPIrERzCxW1HQKhVqUgt_U32LdAyom7jlQ)
SSR build in 5.2.12:
![image](https://private-user-images.githubusercontent.com/18205362/335633797-18a8c6b1-8d2a-4d0a-910e-014af569c07e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjEzNzk2MjMsIm5iZiI6MTcyMTM3OTMyMywicGF0aCI6Ii8xODIwNTM2Mi8zMzU2MzM3OTctMThhOGM2YjEtOGQyYS00ZDBhLTkxMGUtMDE0YWY1NjljMDdlLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzE5VDA4NTUyM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTI0ZDRiMGJmNjY0MWYyN2RlYmU5ODg0Y2ZiODBjNTBjMzk4YWM2NzA1MDUwMzMzNDBjYjdjNTVhYTk4MDllYjYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.0EeEVh_DeXEuX-KFXm5FtUzGORM-eRLCjjTZ-XGIazM)
The file is removed, but it's still referenced in the SSR build, which will cause ERR_MODULE_NOT_FOUND when executing it
Reproduction
https://github.com/meteorlxy/vite-5-2-12-repro
Steps to reproduce
Check the reproduce repo
System Info
Used Package Manager
pnpm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: