-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
[HOLD] workflow: move private packages to separate directory #11520
Conversation
Size ReportBundles
Usages
|
@@ -30,12 +30,13 @@ | |||
"include": [ | |||
"packages/global.d.ts", | |||
"packages/*/src", | |||
"packages-private/*/src", |
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.
It’s a good idea to create a separate tsconfig for packages-private
instead of using the one in the root directory. This way, we’ll have more control over setting the target to esnext
.
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.
ed8754c
to
da49894
Compare
❌ Deploy Preview for vue-sfc-playground failed.
|
❌ Deploy Preview for vue-next-template-explorer failed.
|
Also addes a
vite-debug
package for debugging Vite plugin specific issues.This changes the root directory of both
sfc-playground
andtemplate-explorer
. Since vercel / netlify cannot conditionally specify root dir based on branch, we will have to wait until we moveminor
tomain
after 3.5 release before merging this.