-
Notifications
You must be signed in to change notification settings - Fork 8
Use Wireit for nimble-components build #1267
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
Conversation
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.
Once the build is fixed I'll try it one more time on my dev machine, but it looks great to me! 🎆
I'm gonna move this to draft because it's a bit on the backburner for now and would likely need to be updated to resolve conflicts. Think a good time to revive would be another innovation day. @m-akinc may be useful to split out the karma stuff in a separate review if that plugin is generally useful for the team. The wire-it stuff is a bigger change I want to have to to double check thoroughly before pushing out to everyone. |
@@ -121,3 +121,6 @@ package-lock.json | |||
|
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.
As discussed yesterday moving to draft and assigning to myself to take a look in the future.
Closing as unprioritized right now. Improvements to test / re-test execution likely achievable with typescript incremental build caching and switching to vite builder. Full repo build caching with wireit adds a lot of noise / complexity to npm build scripts. |
Pull Request
🤨 Rationale
I looked into a couple productivity tools for Innovation Day. I'm adding support for Wireit to manage build caching/dependencies for nimble-components package build.
👩💻 Implementation
🧪 Testing
Ran build commands locally
✅ Checklist