-
-
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
Isolate client and server artifacts #3758
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #3758 +/- ##
=========================================
- Coverage 97.92% 97.9% -0.02%
=========================================
Files 18 18
Lines 1158 1147 -11
Branches 311 309 -2
=========================================
- Hits 1134 1123 -11
Misses 23 23
Partials 1 1
Continue to review full report at Codecov.
|
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.
LGTM
How about to extract dist server and client into options.js?
I have considered making these directories configurable, however it adds considerable complexity and I'm not sure it has an use case. |
I don’t think it’s worth making them configurable for now either, what I mean is adding variables in option, so that we only need to resolve one time. |
Regarding putting it to |
That's a Breaking change for CDN deployments but great improvement @ishitatsuyuki 👍 |
@pi0 can you elaborate on why it breaks CDN deployment? You mean when we set |
Correct, we need to update document, user should upload dist/client to cdn. |
@clarkdo like this? nuxt/docs#719 |
Yes and maybe also release notes @Atinux |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Preliminary work for #2517.