[Bug]: stringifyContentPathRegex option not working
jarpoole opened this issue · 1 comments
jarpoole commented
Version
29.0.5
Steps to reproduce
- Clone my MRE repo: https://github.com/jarpoole/mre-ts-jest-stringifyContentPathRegex
- Run
npm install
- Run
npm test
and observe that the import fails
Expected behavior
I expect to be able to use the stringifyContentPathRegex
option to have ts-jest
transform my non-module files into strings at the time of import.
Actual behavior
jest
fails with an error explaining that it cannot parse the file because the syntax is unsupported.
FAIL ./test.spec.ts
● Test suite failed to run
Jest encountered an unexpected token
Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.
Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.
By default "node_modules" folder is ignored by transformers.
Here's what you can do:
• If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
• If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
• To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
• If you need a custom transformation specify a "transform" option in your config.
• If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.
You'll find more details and examples of these config options in the docs:
https://jestjs.io/docs/configuration
For information about custom transformations, see:
https://jestjs.io/docs/code-transformation
Details:
/home/jarpoole/mre-ts-jest-stringifyContentPathRegex/raw.txt:1
({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){hello world
^^^^^
SyntaxError: Unexpected identifier
> 1 | import raw from './raw.txt'
| ^
2 |
3 | describe('some typescript tests', () => {
4 | it('should work with typescript', () => {
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1495:14)
at Object.<anonymous> (test.spec.ts:1:1)
Test Suites: 1 failed, 1 total
Tests: 0 total
Snapshots: 0 total
Time: 1.136 s
Ran all test suites.
Debug log
Additional context
I originally discovered this issue in ts-jest
version 28.0.8
in my main repo so ideally a new patch for this version would be swell.
Environment
System:
OS: Linux 5.15 Ubuntu 20.04.4 LTS (Focal Fossa)
CPU: (32) x64 AMD Ryzen 9 5950X 16-Core Processor
Binaries:
Node: 16.18.1 - ~/.nvm/versions/node/v16.18.1/bin/node
npm: 8.19.2 - ~/.nvm/versions/node/v16.18.1/bin/npm
npmPackages:
jest: ^29.4.3 => 29.4.3
jarpoole commented
Eventually I ended up solving this issue by defining a custom transformer:
module.exports = {
process(sourceText) {
return {
code: `module.exports = ${JSON.stringify(sourceText)}`
}
}
}
(don't forget to reference this transformer in the transform
option with a regex that includes all the right file extensions)