❌ An unexpected error occurred. For more details, check console
Error: The process '/usr/local/bin/yarn' failed with exit code 1
Statements coverage not met for global: expected >=40%, but got 4.709800190294957%
St.:grey_question:
Category
Percentage
Covered / Total
🔴
Statements
4.71% (-45.91% 🔻)
198/4204
🔴
Branches
4.61% (-37.44% 🔻)
85/1845
🔴
Functions
3.93% (-41.06% 🔻)
48/1222
🔴
Lines
4.94% (-45.91% 🔻)
196/3969
:warning: Details were not displayed: the report size has exceeded the limit.
Test suite run failed
Failed tests: 1/90. Failed suites: 32/39.
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/wagmi/dist/index.js:2
import { createSyncStoragePersister } from "@tanstack/query-sync-storage-persister";
^^^^^^
SyntaxError: Cannot use import statement outside a module
7 | import { observer } from 'mobx-react-lite';
8 | import React, { useContext, useState } from 'react';
> 9 | import { useDisconnect } from 'wagmi';
| ^
10 |
11 | import useENS from '../../hooks/useEns';
12 | import { shortenAddress } from '../../utils/componentHelpers';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/components-v2/common/WalletDrawer.tsx:9:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
2 | import { Web3Provider } from '@ethersproject/providers';
3 | import { Box, Button, CircularProgress, makeStyles, Typography } from '@material-ui/core';
> 4 | import { watchAccount, watchNetwork, watchProvider } from '@wagmi/core';
| ^
5 | import { Web3Button } from '@web3modal/react';
6 | import { StoreContext } from 'mobx/stores/store-context';
7 | import { observer } from 'mobx-react-lite';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/components-v2/common/WalletWidget.tsx:4:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@web3modal/react/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import c,{memo as $,useCallback as g,useEffect as i,useState as d}from"react";import{ClientCtrl as P,ConfigCtrl as n,OptionsCtrl as w,ModalCtrl as a}from"@web3modal/core";var E=Object.defineProperty,b=Object.getOwnPropertySymbols,M=Object.prototype.hasOwnProperty,S=Object.prototype.propertyIsEnumerable,p=(t,e,r)=>e in t?E(t,e,{enumerable:!0,configurable:!0,writable:!0,value:r}):t[e]=r,k=(t,e)=>{for(var r in e||(e={}))M.call(e,r)&&p(t,r,e[r]);if(b)for(var r of b(e))S.call(e,r)&&p(t,r,e[r]);return t};function Z(t){return c.createElement("w3m-core-button",k({},t))}var I=Object.defineProperty,s=Object.getOwnPropertySymbols,B=Object.prototype.hasOwnProperty,W=Object.prototype.propertyIsEnumerable,f=(t,e,r)=>e in t?I(t,e,{enumerable:!0,configurable:!0,writable:!0,value:r}):t[e]=r,x=(t,e)=>{for(var r in e||(e={}))B.call(e,r)&&f(t,r,e[r]);if(s)for(var r of s(e))W.call(e,r)&&f(t,r,e[r]);return t};function T(t){return c.createElement("w3m-modal",x({},t))}var V=Object.defineProperty,D=Object.defineProperties,L=Object.getOwnPropertyDescriptors,l=Object.getOwnPropertySymbols,j=Object.prototype.hasOwnProperty,C=Object.prototype.propertyIsEnumerable,m=(t,e,r)=>e in t?V(t,e,{enumerable:!0,configurable:!0,writable:!0,value:r}):t[e]=r,N=(t,e)=>{for(var r in e||(e={}))j.call(e,r)&&m(t,r,e[r]);if(l)for(var r of l(e))C.call(e,r)&&m(t,r,e[r]);return t},U=(t,e)=>D(t,L(e)),q=(t,e)=>{var r={};for(var o in t)j.call(t,o)&&e.indexOf(o)<0&&(r[o]=t[o]);if(t!=null&&l)for(var o of l(t))e.indexOf(o)<0&&C.call(t,o)&&(r[o]=t[o]);return r};function z(t){var e=t,{ethereumClient:r}=e,o=q(e,["ethereumClient"]);const u=g(async()=>{r&&P.setEthereumClient(r),n.setConfig(U(N({},o),{walletConnectVersion:r?.walletConnectVersion})),await import("@web3modal/ui"),w.setIsUiLoaded(!0)},[r,o]);return i(()=>{u()},[u]),c.createElement(T,null)}const _=$(z);var A=Object.defineProperty,v=Object.getOwnPropertySymbols,F=Object.prototype.hasOwnProperty,G=Object.prototype.propertyIsEnumerable,y=(t,e,r)=>e in t?A(t,e,{enumerable:!0,configurable:!0,writable:!0,value:r}):t[e]=r,H=(t,e)=>{for(var r in e||(e={}))F.call(e,r)&&y(t,r,e[r]);if(v)for(var r of v(e))G.call(e,r)&&y(t,r,e[r]);return t};function ee(t){return c.createElement("w3m-network-switch",H({},t))}var J=Object.defineProperty,O=Object.getOwnPropertySymbols,K=Object.prototype.hasOwnProperty,Q=Object.prototype.propertyIsEnumerable,h=(t,e,r)=>e in t?J(t,e,{enumerable:!0,configurable:!0,writable:!0,value:r}):t[e]=r,R=(t,e)=>{for(var r in e||(e={}))K.call(e,r)&&h(t,r,e[r]);if(O)for(var r of O(e))Q.call(e,r)&&h(t,r,e[r]);return t};function re(){const[t,e]=d(a.state);return i(()=>{const r=a.subscribe(o=>e(R({},o)));return()=>{r()}},[]),{isOpen:t.open,open:a.open,close:a.close,setDefaultChain:w.setSelectedChain}}function te(){const[t,e]=d({themeMode:n.state.themeMode,themeColor:n.state.themeColor,themeBackground:n.state.themeBackground});return i(()=>{const r=n.subscribe(o=>e({themeMode:o.themeMode,themeColor:o.themeColor,themeBackground:o.themeBackground}));return()=>{r()}},[]),{theme:t,setTheme:n.setThemeConfig}}export{Z as Web3Button,_ as Web3Modal,ee as Web3NetworkSwitch,re as useWeb3Modal,te as useWeb3ModalTheme};
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { Grid, makeStyles } from '@material-ui/core';
> 2 | import { Web3NetworkSwitch } from '@web3modal/react';
| ^
3 | import React from 'react';
4 |
5 | import WalletWidget from '../common/WalletWidget';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/components-v2/navbar/NavbarButtons.tsx:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● 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.
• 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
Details:
/home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import "./chunk-KX4UEHS5.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module
1 | import { BadgerAPI, BadgerSDK, getNetworkConfig, LogLevel, SDKProvider } from '@badger-dao/sdk';
> 2 | import { fetchSigner } from '@wagmi/core';
| ^
3 | import { defaultNetwork } from 'config/networks.config';
4 | import { action, makeObservable, observable } from 'mobx';
5 | import { RouterStore } from 'mobx-router';
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object. (src/mobx/stores/RootStore.ts:2:1)
```
---
```
● Date Utils › Should return date with timezone
expect(received).toEqual(expected) // deep equality
Expected: "12/1/22, 1:00 AM EST"
Received: "12/1/22, 1:00 AM EST"
3 | describe('Date Utils', () => {
4 | it('Should return date with timezone', () => {
> 5 | expect(getFormatedDateTime(new Date('12/1/22 01:00:00 EST'))).toEqual('12/1/22, 1:00 AM EST');
| ^
6 | });
7 | });
8 |
at Object. (src/tests/date.test.ts:5:67)
at TestScheduler.scheduleTests (node_modules/@jest/core/build/TestScheduler.js:333:13)
at runJest (node_modules/@jest/core/build/runJest.js:404:19)
at _run10000 (node_modules/@jest/core/build/cli/index.js:320:7)
at runCLI (node_modules/@jest/core/build/cli/index.js:173:3)
```
Coverage report
❌ An unexpected error occurred. For more details, check console
Failed tests: 1/90. Failed suites: 32/39.
``` ● 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. • 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 Details: /home/runner/work/v2-ui/v2-ui/node_modules/@wagmi/core/dist/index.js:1 ({"Object.
Report generated by 🧪jest coverage report action from bc31f08346826375193eab0bd900eaad44f2ee7a