add macros plugins with default config rather than no plugins at all #2106
Conversation
This file contains 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
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.
This prevents build failures on missing
@embroider/macrosif you're running with no compatibility prebuild. It doesn't yet expose a way to send additional configuration into the macro system under those conditions, that can be a followup.(The default vite conventions for mode and NODE_ENV mean that we could in theory make this babel config figure out the isDeveloping status via process.NODE_ENV, but
vite build --mode=developmentunfortunately still defaults to NODE_ENV=production, and that's not when we're building test suites for CI.)