Listed the default condition as the last #16
Merged
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
This was referenced Mar 10, 2023
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.
Background
While downstreaming the changes from #14 to
ember-container-query, I realized that thedefaultkey must appear as last in the POJO for'./*'. Otherwise, when we try to build thetest-app, we will encounter errors like the one below:ERROR in cache-233-webpack_bundler_ember_auto_import_webpack/app.cjs 20:82-141 Module not found: Error: Default condition should be last oneIt feels counterintuitive (a technical risk) that the keys of an object have an order dependency.
References
To learn more about
default: