Release 0.14.1 - #682
Merged
Merged
Conversation
Every entry since 0.14.0 touches one blueprint and not the other, and two of them read as though they touched both: the build failure reporting is the classic blueprint's `ember build --watch` path only, and moving to `vite build` leaves `ember build` in place for classic applications. Say so, and put the entries in the order someone upgrading would want them: what changes how their application is built, then what was broken, then what was only untidy. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A Vite-based application is built with vite build, the command its own build script runs, and is recognised from any of the six names Vite resolves its configuration from. A classic application's build failure is reported whole rather than one line of it, and ember build is no longer given --watcher for a build that does not watch. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two commits: the entries are sharpened first, then the section is named and the version bumped.
What 0.14.1 ships
Everything since
0.14.0is about the Vite-based blueprint and how failures from either blueprint are reported. No new options, nothing removed.vite buildrather thanember buildvite.config.*names--watcheronly when the build watchesThe diff since
0.14.0islib/ember_cli/{command,path_set,build_monitor}.rb, their specs, and thesilententry in the README — every one of them covered by an entry.What changed in the entries
The entries were written one PR at a time, and two of them read as though they touched both blueprints:
BuildMonitor, which only sees a classic application'sember build --watchoutputvite buildleavesember buildin place for classic applicationsBoth now say so. The order is what someone upgrading would want: what changes how their application is built, then what was broken, then what was only untidy.
The one behaviour change to notice
silent: trueon a Vite application now runsvite build --logLevel errorinstead ofember build --silent. Progress output is dropped and errors are kept. Everything else — the files a build writes, and the whole of the classic blueprint — is as it was.Version
0.14.1, as a patch: the four changes are fixes and an internal swap of the build command, with the build output unchanged. Thesilentmapping above is the only user-visible difference, and it affects an option's verbosity rather than its meaning. Say the word if you would rather this went out as0.15.0.🤖 Generated with Claude Code