-
Notifications
You must be signed in to change notification settings - Fork 915
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
why ssr module registration was removed from v16 #1887
Comments
Please be more specific. I don't understand what you mean by "ssr module registration" |
sorry. version 15.x of vue-loader will use the following code to add the component during ssr rendering, the code is located in lib/runtime/componentNormalizer.js
|
Oh, that was a planned but not yet implemented feature. Thanks for bringing this up. Contributions are also welcome. |
Hi @sodatea. I've implemented critical CSS collection in https://github.com/phoenix-ru/vue-loader. However, my solution assumes that If that solution is fine, I can open a PR and polish it |
Hello, any plans? |
@dmitryuk I don't think so. There is a open PR since August by @niksy #2083 It will be only worst. The rolldown comming up, so I think they will drop support for Webpack any time soon. Last commit in this repo was 10 months ago. We've made a fork for our purposes, add patch by niks and seams to work fine for us. |
This is really unfortunate becuase Vue loader will probably still be actively used because of Rspack and it’s Vue support. The other solution (and probably best approach) can be unplugin-vue, but it’s missing HMR support for Webpack/Rspack. |
Version
16.8.1
Reproduction link
github.com
Steps to reproduce
i have no idea why the functionality was removed. it's very important for ssr rendering.
vitejs/plugin-vue and vue-loader are both plugins, why vitejs/plugin-vue has this functionality but vue-loader doesnt
What is expected?
ssr module registration should be support
What is actually happening?
ssr module registration was removed
The text was updated successfully, but these errors were encountered: