Describe the bug
When working with Angular in an NX workspace and writing unit tests with Jest I can not import Clarity components without braking the tests.
How to reproduce
I am using an NX workspace with Angular preset and install @cds packages.
npx create-nx-workspace@latest
npm i @cds/{core,angular} --legacy-peer-deps
Then, if a clarity component is part of a Jest unit test, for example:
import { TestBed } from '@angular/core/testing';
import { CdsButtonModule } from '@cds/angular'; // <---
import { AppComponent } from './app.component';
import { NxWelcomeComponent } from './nx-welcome.component';
describe('AppComponent', () => {
beforeEach(async () => {
await TestBed.configureTestingModule({
imports: [CdsButtonModule], // <---
declarations: [AppComponent, NxWelcomeComponent],
}).compileComponents();
});
});
It is throwing:
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
/PATHTO/clarity-jest-test/node_modules/@cds/core/accordion/register.js:1
({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import{registerElementSafely as o,ClarityMotion as r,AnimationAccordionPanelOpenName as c,AnimationAccordionPanelOpenConfig as e}from"@cds/core/internal";import{CdsAccordion as n}from"./accordion.element.js";import{CdsAccordionPanel as d}from"./accordion-panel.element.js";import{CdsAccordionContent as t}from"./accordion-content.element.js";import{CdsAccordionHeader as i}from"./accordion-header.element.js";import"@cds/core/icon/register.js";import"@cds/core/button-expand/register.js";o("cds-accordion",n),o("cds-accordion-panel",d),o("cds-accordion-content",t),o("cds-accordion-header",i),r.add(c,e);
^^^^^^
SyntaxError: Cannot use import statement outside a module
at Runtime.createScriptFromCode (../../node_modules/jest-runtime/build/index.js:1796:14)
Here is a demo repository https://github.com/ngfelixl/clarity-jest-test
Expected behavior
I would expect that the components can be used and imported in Jest unit tests.
Versions
Clarity project:
- [x] Clarity Core
- [x] Clarity Angular/UI
Clarity version:
Framework:
- [x] Angular
- [ ] React
- [ ] Vue
- [ ] Other:
Framework version:
"@angular/core": "14.0.5",
"@cds/angular": "6.1.4",
"@cds/core": "6.1.4",
"@nrwl/jest": "14.4.2",
"jest": "27.5.1",
"jest-preset-angular": "11.1.2",
Device:
- Type: Macbook
- OS: macOS Monterey
Contains the Web Components that work in any JavaScript framework.
Contains shims for core usage in Angular environment
Contains shims for core usage in React environment
Our open source sans-serif typeface.
Abnormal (1 result)
18.4k Jan 4, 2023
6.2k Jan 3, 2023
4.7k Jan 4, 2023
17.6k Jan 9, 2023
20.7k Dec 31, 2022
7 Dec 18, 2022
65 Dec 26, 2022
72 Jan 1, 2023
39 Jan 2, 2023
4.3k Jan 5, 2023
75.9k Jan 9, 2023
8.7k Jan 4, 2023
14 Dec 24, 2022
9.7k Dec 30, 2022
4.1k Jan 2, 2023
255 Dec 22, 2022
166 Sep 17, 2022
17 Aug 18, 2022