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
Hello, I'm tring to test the usage of the component but thows me this error
● 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:
/home/rnunez/src/genesis-web/node_modules/vue2-leaflet-fullscreen/LControlFullscreen.vue:1
({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){<script>
^
SyntaxError: Unexpected token '<'
48 | <script>
49 | import {LMap, LTileLayer, LTooltip, LIcon, LPopup} from 'vue2-leaflet'
> 50 | import LControlFullscreen from 'vue2-leaflet-fullscreen'
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1479:14)
Hi @rnunezherrer , not sure if you've had any luck with this yet, but it does not appear to be a problem with vue2-leaflet-fullscreen as far as I can tell, as much as the Jest configuration. Based on the help output you reported, it looks to me as if you might need to specify a custom "transformIgnorePatterns" in your config to have some of your "node_modules" files transformed, since by default "node_modules" folder is ignored by transformers. Perhaps something like
Hello, I'm tring to test the usage of the component but thows me this error
Aparently it is because is not transformed
I have this in my jest.config.js
The text was updated successfully, but these errors were encountered: