-
-
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
class missing #3084
Comments
Hello @MQYForverT. Please provide a online reproduction by codesandbox or a minimal GitHub repository. Issues labeled by |
After upgrading to 2.2.1 this week a whole bunch of CSS related to my application disappeared, and we had to rollback to 2.1.5. This looks like a similar issue: some of our CSS got bundled, but much of it just didn't get included any more. |
@kwesterfeld2 could you try to create reproduction of this issue? |
I don't have a link for you to reproduce, but I can describe the scene for you,Or you can download demo and try it yourself It is to define a static route, add routes to the router, and the typed packet style is normal. If you use glob to dynamically introduce routes, add routes to the router, and the typed packet style will be lost I'm sure! Using glob to dynamically introduce routes, the generated route table is exactly the same as the statically defined route table! |
i have the same issue and here's a reproduction: const a = () => __vitePreload(() => __import__("./a.9ce71214.js"), true ? ["/assets/a.9ce71214.js","/assets/common.module.4b52b9d5.js","/assets/common.module.816a14f3.css","/assets/vendor.c97e27de.js"] : void 0);
const b = () => __vitePreload(() => __import__("./b.eebe1df7.js"), true ? void 0 : void 0);
|
@wuyiw @MQYForverT @kwesterfeld2 the fix was released in Vite v2.2.3, you should be able to update to it in your projects |
@patak-js thanks for the mention, I upgraded and I can confirm this issue is fixed for me. |
This reverts commit 1451b78.
Use glob to dynamically add routes. After packaging, it is found that the class inside the component is not packaged
The text was updated successfully, but these errors were encountered: