Use @swc/jest instead of ts-jest where applicable #407
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
fpauer
added a commit
that referenced
this pull request
Nov 15, 2024
Co-authored-by: Fernando Pauer <pauerf@amazon.com>
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.
Overview
@swc/jestwas recently found as a "faster drop in replacement for ts-jest". We see non-insignificant speed increases using this rust-based package overts-jest.This pull request updates applicable packages to use
@swc/jestwhere it makes sense. Some notes:@swc/jestdoesn't work withstencildecorators. there is an open issue. Decorators on methods in object literals swc-project/swc#3062the scene-composer package still relies on ts-jest for it's configuration, only the transformer was updated
source-iotsitewise and source-iottwinmaker tests weren't running before based on a clean install from the main branch, now they do. I'm unable to provide stats on any potential speed improvements.
any previously failing tests were left that way. there are a small number of these. these will be addressed at a later time.
I think we can get rid of a lot of the babel plugins by using
@swc/jest. It'll require more investigation on a per-package basis to see what can and can't be removed.Legal
This project is available under the Apache 2.0 License.