-
Notifications
You must be signed in to change notification settings - Fork 336
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
Use --build
#487
Use --build
#487
Conversation
Thanks for pointing this out. I didn't actually know this existed and behaved this way. Sadly I don't think this is quite such a magic bullet as it seems, but it's still a strict benefit and we should do it. The thing that's missed from the timing data is that Generally you're going to run this command when you've changed something, so I don't think this is going to make things faster in the common case, but it is still better in the case where there's nothing to do so we should still make this change. |
@RA80533, the CI is complaining that the node modules are out of date, but what it really is I think is that trailing newline in |
Your observation is correct and I should’ve been more specific in my metrics. Builds during development should ultimately end up being much faster, with the ~1,300% increase being the ceiling when no changes have been made. Enabling I’ll run those commands on the branch when I get home. |
It appears that |
Did you also run |
Thanks for sticking with this change! |
Merge / deployment checklist
Before
After
The change results in ~1,300% faster builds.
Closes #486