-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
@vitejs/plugin-legacy support only output legacy bundle #9050
Comments
Hello @xiaoxiangmoe. We like your proposal/feedback and would appreciate a contribution via a Pull Request by you or another community member. We thank you in advance for your contribution and are looking forward to reviewing it! |
Hi @xiaoxiangmoe , could you try this feature? I used |
@sangquangnguyen would you create a new issue with a minimal reproduction linking to the issue and PR? Thanks! |
Ah, sorry for bothering you 😅 , I just want to have a quick check whether the author of this issue encountered another issue like me or this function works well on their end. I might have some wrong configs, let me do more investigations and create a ticket with the details if needed, thanks @patak-dev for your time ❤️ |
I found out the reason, I saw in |
Description
In vue-cli v5,
vue-cli-service build --no-module
will only output the legacy bundles that support all target browsers (loaded via plain<script>
s). See Vue CLI --no-moduleBut @vitejs/plugin-legacy will output both modern and legacy codes.
Suggested solution
Can we add
--no-module
config in vite-plugin-legacy?Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: