You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Bud process does not return the proper exit code when an error occurs
Expected Behavior
The process should return an exit status that isn't 0
This is critical for app deploys to fail as expected when a build doesn't complete. If a build fails but the deploy still continues, then the app can be deployed and immediately break
(Props to @joshuafredrickson for raising this on the #bud channel in the Roots Discord server)
- throw hands on bad compilations
- throw hands on bad configs
still takes the peaceful route when `bud.isDevelopment`
refers:
- #1698
## Type of change
**PATCH: backwards compatible change**
This PR includes breaking changes to the following core packages:
- none
This PR includes breaking changes to the follow extensions:
- none
## Dependencies
### Adds
- none
### Removes
- none
Describe the issue
The Bud process does not return the proper exit code when an error occurs
Expected Behavior
The process should return an exit status that isn't 0
This is critical for app deploys to fail as expected when a build doesn't complete. If a build fails but the deploy still continues, then the app can be deployed and immediately break
(Props to @joshuafredrickson for raising this on the #bud channel in the Roots Discord server)
Actual Behavior
The process returns with an exit status of 0
Steps To Reproduce
yarn add @roots/bud-eslint @roots/eslint-config --dev
.eslintrc.cjs
in the projectapp.js
to produce an errorExample
.eslintrc.cjs
:Example
app.js
:Example simple
test.sh
script to return the code:version
At least 6.3.5 and 6.4.1 are affected
The text was updated successfully, but these errors were encountered: