chore: mention @swc/jest specifically

README.md

@@ -6,22 +6,21 @@ Many companies are successfully testing with rules_jest. If you're getting value
 
 rules_jest is just a part of what Aspect provides:
 
-- _Need help?_ This ruleset has support provided by https://aspect.build/services
+- _Need help?_ This ruleset has support provided by https://aspect.build/services.
 - See our other Bazel rules, especially those built for rules_js, such as rules_ts for TypeScript: https://github.com/aspect-build
 
 ## Installation
 
-From the release you wish to use:
+Follow instructions from the release you wish to use:
 <https://github.com/aspect-build/rules_jest/releases>
-copy the WORKSPACE snippet into your `WORKSPACE` file.
 
 ## Usage
 
 Run all Jest tests in the workspace: `bazel test --test_lang_filters=jest //...`
 
 See [jest_test](docs/jest_test.md) API documentation and the example usages in the [example](https://github.com/aspect-build/rules_jest/tree/main/example/) folder.
 
-> Note that the example also relies on code in the `/WORKSPACE` file in the root of this repo.
+> Note that the example also relies on code in the `/MODULE.bazel` file in the root of this repo.
 
 ## Troubleshooting and common challenges
 

docs/troubleshooting.md

@@ -50,17 +50,17 @@ _Note_: If you are importing a preset, and _it_ declares its own `haste` config,
 
 ## Pre-transpiled sources
 
-Frequently outside the Bazel ecosystem sources such as `*.ts` are transpiled on the fly using tools such as `ts-jest` or `babel-jest`. Such tools are designed for Jest and transpile to a javascript format ideal for Jest but normally not for production use.
+Frequently outside the Bazel ecosystem sources such as `*.ts` are transpiled on the fly using tools such as `ts-jest`, `babel-jest`, or `@swc/jest`. Such tools are designed for Jest and transpile to a javascript format ideal for Jest but normally not for production use.
 
-Transpiling in bazel is normally done ahead of time to take advantage of bazel caching, ensure that the build is hermetic, ensure the tested code is the same as production code etc. However this transpiling is no longer designed specifically for Jest like `ts-jest` or `babel-jest` which may lead to certain limitations. For example:
+Transpiling in bazel is normally done ahead of time to take advantage of bazel caching, ensure that the build is hermetic, and to ensure the tested code is the same as production code. However this transpiling is no longer designed specifically for Jest like `ts-jest` or `babel-jest` which may lead to certain limitations. For example:
 
 ### Runtime tsconfig dependency
 
 If a plugin such as `ts-jest` or `ts-node` is replaced with `rules_ts` (to pre-compile ts files instead of runtime compilation), features such as runtime `tsconfig` path mapping must be replaced with other tools such as `tsconfig-paths`.
 
 ### ESM Modules
 
-Normally Jest uses CommonJS modules (such as when `ts-jest` or `babel-jest` does transpiling on the fly), but with bazel the transpiled sources are normally pre-transpiled and remain as native ESM modules for optimal use by bundlers and other tools.
+Normally Jest uses CommonJS modules (such as when `ts-jest`, `babel-jest`, or `@swc/jest` does transpiling on the fly), but with Bazel the transpiled sources are normally pre-transpiled and remain as native ESM modules for optimal use by bundlers and other tools.
 
 ESM modules come with certain challenges in NodeJS and therefor also in Jest, see:
 

e2e/swc/README.md

@@ -1,5 +1,7 @@
 # Example showing usage and challenges using rules_jest with swc (via rules_swc)
 
+NB: this example predates the https://swc.rs/docs/usage/jest package, which likely solves these problems.
+
 ## Mocking of esm exports when transforming to commonjs
 
 When transforming esm to commonjs, swc defines the exports as readonly.