You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jest encountered an unexpected token
This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.
By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".
Here's what you can do:
• 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/en/configuration.html
Details:
/private/tmp/taskbox-angular-sb3/src/app/app.component.spec.ts:1
({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import { TestBed, async } from '@angular/core/testing';
^^^^^^
SyntaxError: Unexpected token import
at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/script_transformer.js:403:17)
NOTE: this is with @storybook/angular@rc -- the 4.0 version. SB3.4 doesn't work with the new angular CLI at all.
I think due to the new angular CLI version, when following the instructions on https://www.learnstorybook.com/angular/en/simple-component/ to install and use jest, I get babel errors -- maybe we need to setup jest slightly differently?
NOTE: this is with
@storybook/angular@rc
-- the 4.0 version. SB3.4 doesn't work with the new angular CLI at all.SECOND NOTE: to get storyshots working again there are some other small changes required, see this commit for hints: https://github.com/chromaui/learnstorybook.com/pull/59/files#diff-4501e37952bca452aa3f7d49ac721bee
The text was updated successfully, but these errors were encountered: