Skip to content
This repository has been archived by the owner on Aug 19, 2019. It is now read-only.

On windows setting node_env won't work #6

Open
paulvanbladel opened this issue Nov 4, 2018 · 1 comment
Open

On windows setting node_env won't work #6

paulvanbladel opened this issue Nov 4, 2018 · 1 comment

Comments

@paulvanbladel
Copy link

paulvanbladel commented Nov 4, 2018

windows requires in package.json:
"test:unit": "set NODE_ENV=dev jest",

use: https://www.npmjs.com/package/cross-env

@paulvanbladel
Copy link
Author

Very interesting repo but...
Seems to be more problems on windows:

$ yarn test:unit
yarn run v1.9.4
$ set NODE_ENV=dev && jest
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ssr-starter-kit
  Paths: E:\GITHUB3RD\quasar-starter-ssr-pwa-jest-cypress\package.json collides with E:\GITHUB3RD\quasar-starter-ssr-pwa-jest-cypress\dist\ssr-mat\package.json

This warning is caused by a @providesModule declaration with the same name across two different files.
 FAIL  test/jest/components/QBtn.spec.js
  ● Test suite failed to run

    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:

    E:\GITHUB3RD\quasar-starter-ssr-pwa-jest-cypress\test\jest\components\QBtn.spec.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import "core-js/modules/es6.array.find";
                                                                                             ^^^^^^

    SyntaxError: Unexpected token import

      at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/script_transformer.js:403:17)

 FAIL  test/jest/Math.test.js
  ● Test suite failed to run

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant