-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
chore: filter demo projects from packages #3276
chore: filter demo projects from packages #3276
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
CodSpeed Performance ReportMerging #3276 will not alter performanceComparing Summary
|
Coverage Report:
Changed Files:Coverage values did not change👌. |
@@ -12,7 +12,7 @@ | |||
"scripts": { | |||
"dev": "nodemon --config nodemon.config.json -x 'pnpm build:packages'", | |||
"build": "turbo run build --cache-dir=.turbo", | |||
"build:packages": "turbo run build --filter=!docs --filter=!template-*", | |||
"build:packages": "turbo run build --filter=!docs --filter=!template-* --filter=!demo-*", |
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.
Demos were made to serve as test/validators.
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.
Demos were made to serve as test/validators.
@arboleya I suppose I thought the build:packages
command should only be responsible for building the packages.
Then the build
command would be build
+ validate
as you say.
Thoughts?
Closing as no planned |
Summary
demo
application builds for thebuild:packages
command.Checklist