Make Jest configs runnable scripts #432
Merged
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.
Getting Jest to work with ESM modules has been painful, and the guide at https://jestjs.io/docs/ecmascript-modules doesn't seem to work when the Jest config is in a TypeScript file.
Since I'm stubborn, I decided to try to find a workaround, and I found this one! We make the config a runnable script that runs the Jest command, rather than relying on the Jest command to read the config. This is a bit funny, but it seems to work, because Jest requires configuration to be JSON-serializable: https://jestjs.io/docs/configuration and the command-line config option (https://jestjs.io/docs/cli#--configpath) accepts a JSON string!