Fix the 0.7 release #152
Merged
Fix the 0.7 release #152
Conversation
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
Sets it back to the old release style. The thing produced by wasm-pack is a ES/nodenext module, but our shim still wraps it into a CJS module, so downstream consumers don't need to change anything. We lose our TS compile checking the validity of dependencies types (though our uses of them are still checked against their declarations). We do this on most (all?) of our other TS projects.
|
Minimum allowed coverage is Generated by 🐒 cobertura-action against d5aada7 |
giarc3
approved these changes
Nov 18, 2025
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.
Sets it back to the old release style. The thing produced by wasm-pack is a ES/nodenext module, but our shim still wraps it into a CJS module, so downstream consumers don't need to change anything. We lose our TS compile checking the validity of dependencies types (though our uses of them are still checked against their declarations). We do this on most (all?) of our other TS projects.
We should probably deprecate
0.7.0, though it did technically work for consumers that had the right mix of bundling voodoo (for exironweb's consumption of it worked), it could've been a more breaking change than intended for consumers.