-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
fix($core): no dynamic import style #1490
Conversation
What do you mean with empty chunk? I don't see empty chunks in https://github.com/Shigma/vuepress-generates-empty-chunk/tree/master/.vuepress/dist |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job, and could you help confirm following 2 things:
- Whether the generated CSS styles satisfies the following sequence - ref:
- Theme's styles
- User's styles
- The underlying causes of generating this empty chunk.
vuepress/packages/docs/docs/.vuepress/styles/index.styl Lines 3 to 5 in a973960
And it works as expected.
|
@ulivz Can you look into this PR one more time? |
hello @shigma i know it's been a while. But can you tell me more about your PR. What about the empty chunks stuff. I think about the generation of them. It's look great but i am not sure to understand |
Can we have this PR merged? I think it is using the improt function which the webpack provides now, and he is changing it to es module syntax. So it will fix the empty chunk issue. @f3ltron |
@f3ltron
|
@newsbielt703 @meteorlxy Could you check and merge this PR. Quite a long time since Shigma opened it. |
LGTM! One more approval and it will be merged. |
Glad to see this merged. Thanks! |
Summary
VuePress will create an empty chunk every time.
repro: https://github.com/Shigma/vuepress-generates-empty-chunk
What kind of change does this PR introduce? (check at least one)
If changing the UI of default theme, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
fix #xxx[,#xxx]
, where "xxx" is the issue number)You have tested in the following browsers: (Providing a detailed version will be better.)
If adding a new feature, the PR's description includes:
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information: