NGRX Traits is a library to help you compose and reuse state logic in your angular app. There is two versions, @ngrx-traits/signals supports ngrx-signals, and @ngrx-traits/{core, common} supports ngrx.
The following error is received when a test imports anything from ngrx-traits
FAIL
● 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.
• 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:
../node_modules/ngrx-traits/ngrx-traits.d.ts:5
export * from './public_api';
^^^^^^
SyntaxError: Unexpected token 'export'
> 1 | import { createEntityFeatureFactory } from 'ngrx-traits';
| ^
at Runtime.createScriptFromCode (../../node_modules/jest-runtime/build/index.js:1479:14)
I believe this issue was due to the built files missing the FESM and UMD builds, as the ng-package-lite builder was used instead of the full one. After switching the builder, this issue does not happen anymore
The following error is received when a test imports anything from ngrx-traits