ge';

14 |
15 | export default class Component extends React.Component {

at ScriptTransformer._transformAndBuildScript
(node_modules/@jest/transform/build/ScriptTransformer.js:537:17)
at ScriptTransformer.transform
(node_modules/@jest/transform/build/ScriptTransformer.js:579:25)
at Object.<anonymous> (src/components/layouts/PageBase/component.js:12:1)

FAIL src/components/pages/FlashSale/__tests__/component.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:

/var/lib/jenkins/workspace/ndonesia-marketplace-dev_develop/src/components/
elements/UserMenu/index.js:111
return import('./component');
^^^^^^

SyntaxError: Unexpected token import

10 | import SocialIcon from '../../elements/SocialIcon';

11 | import SearchToolbar from '../../elements/SearchToolbar';
> 12 | import UserMenu from '../../elements/UserMenu';
| ^
13 | import SnackbarMessage from '../../elements/SnackbarMessage';
14 |
15 | export default class Component extends React.Component {

at ScriptTransformer._transformAndBuildScript
(node_modules/@jest/transform/build/ScriptTransformer.js:537:17)
at ScriptTransformer.transform
(node_modules/@jest/transform/build/ScriptTransformer.js:579:25)
at Object.<anonymous> (src/components/layouts/PageBase/component.js:12:1)

FAIL src/components/pages/Cart/__tests__/index.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:

/var/lib/jenkins/workspace/ndonesia-marketplace-dev_develop/src/components/
elements/UserMenu/index.js:111
return import('./component');
^^^^^^

SyntaxError: Unexpected token import

10 | import SocialIcon from '../../elements/SocialIcon';

11 | import SearchToolbar from '../../elements/SearchToolbar';
> 12 | import UserMenu from '../../elements/UserMenu';
| ^
13 | import SnackbarMessage from '../../elements/SnackbarMessage';
14 |
15 | export default class Component extends React.Component {

at ScriptTransformer._transformAndBuildScript
(node_modules/@jest/transform/build/ScriptTransformer.js:537:17)
at ScriptTransformer.transform
(node_modules/@jest/transform/build/ScriptTransformer.js:579:25)
at Object.<anonymous> (src/components/layouts/PageBase/component.js:12:1)

FAIL src/components/pages/Cart/__tests__/component.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:

/var/lib/jenkins/workspace/ndonesia-marketplace-dev_develop/src/components/
elements/UserMenu/index.js:111
return import('./component');
^^^^^^

SyntaxError: Unexpected token import

10 | import SocialIcon from '../../elements/SocialIcon';

11 | import SearchToolbar from '../../elements/SearchToolbar';
> 12 | import UserMenu from '../../elements/UserMenu';
| ^
13 | import SnackbarMessage from '../../elements/SnackbarMessage';
14 |
15 | export default class Component extends React.Component {

at ScriptTransformer._transformAndBuildScript
(node_modules/@jest/transform/build/ScriptTransformer.js:537:17)
at ScriptTransformer.transform
(node_modules/@jest/transform/build/ScriptTransformer.js:579:25)
at Object.<anonymous> (src/components/layouts/PageBase/component.js:12:1)

FAIL src/components/pages/News/__tests__/index.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:

/var/lib/jenkins/workspace/ndonesia-marketplace-dev_develop/src/components/
elements/UserMenu/index.js:111
return import('./component');
^^^^^^

SyntaxError: Unexpected token import

10 | import SocialIcon from '../../elements/SocialIcon';

 11 | import SearchToolbar from '../../elements/SearchToolbar';
> 12 | import UserMenu from '../../elements/UserMenu';
| ^
13 | import SnackbarMessage from '../../elements/SnackbarMessage';
14 |
15 | export default class Component extends React.Component {

at ScriptTransformer._transformAndBuildScript
(node_modules/@jest/transform/build/ScriptTransformer.js:537:17)
at ScriptTransformer.transform
(node_modules/@jest/transform/build/ScriptTransformer.js:579:25)
at Object.<anonymous> (src/components/layouts/PageBase/component.js:12:1)

FAIL src/components/pages/Profile/__tests__/index.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:

/var/lib/jenkins/workspace/ndonesia-marketplace-dev_develop/src/components/
elements/UserMenu/index.js:111
return import('./component');
^^^^^^

SyntaxError: Unexpected token import

10 | import SocialIcon from '../../elements/SocialIcon';

11 | import SearchToolbar from '../../elements/SearchToolbar';
> 12 | import UserMenu from '../../elements/UserMenu';
| ^
13 | import SnackbarMessage from '../../elements/SnackbarMessage';
14 |
15 | export default class Component extends React.Component {

at ScriptTransformer._transformAndBuildScript
(node_modules/@jest/transform/build/ScriptTransformer.js:537:17)
at ScriptTransformer.transform
(node_modules/@jest/transform/build/ScriptTransformer.js:579:25)
at Object.<anonymous> (src/components/layouts/PageBase/component.js:12:1)
Test Suites: 68 failed, 194 passed, 262 total
Tests: 15 failed, 796 passed, 811 total
Snapshots: 54 passed, 54 total
Time: 155.535s
Ran all test suites.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! codebase-frontend-ssr@1.0.0 test: `jest "--coverage"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the codebase-frontend-ssr@1.0.0 test script.
npm ERR! This is probably not a problem with npm. There is likely additional
logging output above.

npm ERR! A complete log of this run can be found in:

npm ERR! /var/lib/jenkins/.npm/_logs/2021-02-26T03_47_25_941Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! codebase-frontend-ssr@1.0.0 test:cover: `npm run test -- --coverage `
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the codebase-frontend-ssr@1.0.0 test:cover script.
npm ERR! This is probably not a problem with npm. There is likely additional
logging output above.

npm ERR! A complete log of this run can be found in:

npm ERR! /var/lib/jenkins/.npm/_logs/2021-02-26T03_47_25_948Z-debug.log