Pastein: 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

Загрузка данных
 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { clamp } from 'lodash-es';
        | ^
      2 |
      3 | import type { Anchor, Bounds, ContainerSize, Point, SeriesApi } from './types';
      4 |

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/helpers.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/regressionTrend/regressionTrend.ts:7:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/drawings/regressionTrend.test.ts:3:1)

 FAIL  src/core/Drawings/__tests__/drawings/traectory.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

      1 | import { IPrimitivePaneView, PrimitiveHoveredItem } from 'lightweight-charts';
    > 2 | import { clamp } from 'lodash-es';
        | ^
      3 |
      4 | import { CustomPriceAxisPaneView, CustomTimeAxisPaneView } from '@core/Drawings/axis';
      5 | import {

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/traectory/traectory.ts:2:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/drawings/traectory.test.ts:4:1)

 FAIL  src/core/Drawings/__tests__/drawings/text.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

      1 | import { IPrimitivePaneView, PrimitiveHoveredItem, TouchMouseEventData, UTCTimestamp } from 'lightweight-charts';
    > 2 | import { clamp } from 'lodash-es';
        | ^
      3 |
      4 | import { CustomPriceAxisView, CustomTimeAxisView } from '@core/Drawings/axis';
      5 | import {

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/text/text.ts:2:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/drawings/text.test.ts:4:1)

 FAIL  src/core/Drawings/__tests__/drawingTestUtils.ts
  ● Test suite failed to run

    Your test suite must contain at least one test.

      at onResult (node_modules/@jest/core/build/TestScheduler.js:133:18)
      at node_modules/@jest/core/build/TestScheduler.js:254:19
      at node_modules/emittery/index.js:363:13
          at Array.map (<anonymous>)
      at Emittery.emit (node_modules/emittery/index.js:361:23)

 PASS  src/core/Drawings/__tests__/drawings/CustomPriceAxis.test.ts
 FAIL  src/core/Drawings/__tests__/drawings/ruler.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { clamp } from 'lodash-es';
        | ^
      2 |
      3 | import type { Anchor, Bounds, ContainerSize, Point, SeriesApi } from './types';
      4 |

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/helpers.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/ruler/ruler.ts:10:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/drawings/ruler.test.ts:5:1)

 PASS  src/core/Drawings/__tests__/drawings/CustomTimeAxis.test.ts
 PASS  src/core/Drawings/__tests__/utils.test.ts
 FAIL  src/core/Drawings/__tests__/shortcuts.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { clamp } from 'lodash-es';
        | ^
      2 |
      3 | import type { Anchor, Bounds, ContainerSize, Point, SeriesApi } from './types';
      4 |

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/helpers.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/axisLine/axisLine.ts:2:1)
      at Object.<anonymous> (src/core/Drawings/axisLine/index.ts:1:1)
      at Object.<anonymous> (src/constants/drawing.ts:1:1)
      at Object.<anonymous> (src/constants/index.ts:3:1)
      at Object.<anonymous> (src/core/Drawings/shortcuts.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/shortcuts.test.ts:1:1)

 PASS  src/core/__tests__/Legend.test.ts
 PASS  src/core/__tests__/ContainerManager.test.ts
 PASS  src/components/__tests__/LegendComponent.test.tsx
 PASS  src/components/__tests__/ChartTooltip.test.tsx

Summary of all failing tests
 FAIL  src/core/Drawings/__tests__/drawings/diapson.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { clamp } from 'lodash-es';
        | ^
      2 |
      3 | import {
      4 |   CustomPriceAxisPaneView,

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/diapson/diapson.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/drawings/diapson.test.ts:1:1)

 FAIL  src/core/Drawings/__tests__/drawings/axisLine.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { clamp } from 'lodash-es';
        | ^
      2 |
      3 | import type { Anchor, Bounds, ContainerSize, Point, SeriesApi } from './types';
      4 |

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/helpers.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/axisLine/axisLine.ts:2:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/drawings/axisLine.test.ts:1:1)

 FAIL  src/core/Drawings/__tests__/SeriesDrawingBase.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { clamp } from 'lodash-es';
        | ^
      2 |
      3 | import type { Anchor, Bounds, ContainerSize, Point, SeriesApi } from './types';
      4 |

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/helpers.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/handles.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/SeriesDrawingBase.test.ts:3:1)

 FAIL  src/core/Drawings/__tests__/drawings/fibonacciRetracement.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { clamp } from 'lodash-es';
        | ^
      2 |
      3 | import {
      4 |   CustomPriceAxisPaneView,

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/fibonacciRetracement/fibonacciRetracement.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/drawings/fibonacciRetracement.test.ts:1:1)

 FAIL  src/core/Drawings/__tests__/drawings/volumeProfile.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

      1 | import { IPrimitivePaneView, PrimitiveHoveredItem, Time, UTCTimestamp } from 'lightweight-charts';
    > 2 | import { clamp } from 'lodash-es';
        | ^
      3 |
      4 | import {
      5 |   CustomPriceAxisPaneView,

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/volumeProfile/volumeProfile.ts:2:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/drawings/volumeProfile.test.ts:4:1)

 FAIL  src/core/Drawings/__tests__/helpers.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { clamp } from 'lodash-es';
        | ^
      2 |
      3 | import type { Anchor, Bounds, ContainerSize, Point, SeriesApi } from './types';
      4 |

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/helpers.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/helpers.test.ts:1:1)

 FAIL  src/core/Drawings/__tests__/drawings/rectangle.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { clamp } from 'lodash-es';
        | ^
      2 |
      3 | import {
      4 |   CustomPriceAxisPaneView,

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/rectangle/rectangle.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/drawings/rectangle.test.ts:3:1)

 FAIL  src/core/Drawings/__tests__/drawings/sliderPosition.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { clamp } from 'lodash-es';
        | ^
      2 |
      3 | import type { Anchor, Bounds, ContainerSize, Point, SeriesApi } from './types';
      4 |

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/helpers.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/sliderPosition/sliderPosition.ts:9:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/drawings/sliderPosition.test.ts:4:1)

 FAIL  src/core/Drawings/__tests__/drawings/parallelChannel.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { clamp } from 'lodash-es';
        | ^
      2 |
      3 | import type { Anchor, Bounds, ContainerSize, Point, SeriesApi } from './types';
      4 |

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/helpers.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/parallelChannel/parallelChannel.ts:9:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/drawings/parallelChannel.test.ts:3:1)

 FAIL  src/core/Drawings/__tests__/drawings/line.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { clamp } from 'lodash-es';
        | ^
      2 |
      3 | import type { Anchor, Bounds, ContainerSize, Point, SeriesApi } from './types';
      4 |

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/helpers.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/line/lineDrawing.ts:9:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/drawings/line.test.ts:1:1)

 FAIL  src/core/Drawings/__tests__/drawings/ray.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { clamp } from 'lodash-es';
        | ^
      2 |
      3 | import type { Anchor, Bounds, ContainerSize, Point, SeriesApi } from './types';
      4 |

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/helpers.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/ray/ray.ts:9:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/drawings/ray.test.ts:3:1)

 FAIL  src/core/Drawings/__tests__/handles.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { clamp } from 'lodash-es';
        | ^
      2 |
      3 | import type { Anchor, Bounds, ContainerSize, Point, SeriesApi } from './types';
      4 |

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/helpers.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/handles.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/handles.test.ts:1:1)

 FAIL  src/core/Drawings/__tests__/drawings/regressionTrend.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { clamp } from 'lodash-es';
        | ^
      2 |
      3 | import type { Anchor, Bounds, ContainerSize, Point, SeriesApi } from './types';
      4 |

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/helpers.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/regressionTrend/regressionTrend.ts:7:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/drawings/regressionTrend.test.ts:3:1)

 FAIL  src/core/Drawings/__tests__/drawings/traectory.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

      1 | import { IPrimitivePaneView, PrimitiveHoveredItem } from 'lightweight-charts';
    > 2 | import { clamp } from 'lodash-es';
        | ^
      3 |
      4 | import { CustomPriceAxisPaneView, CustomTimeAxisPaneView } from '@core/Drawings/axis';
      5 | import {

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/traectory/traectory.ts:2:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/drawings/traectory.test.ts:4:1)

 FAIL  src/core/Drawings/__tests__/drawings/text.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

      1 | import { IPrimitivePaneView, PrimitiveHoveredItem, TouchMouseEventData, UTCTimestamp } from 'lightweight-charts';
    > 2 | import { clamp } from 'lodash-es';
        | ^
      3 |
      4 | import { CustomPriceAxisView, CustomTimeAxisView } from '@core/Drawings/axis';
      5 | import {

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/text/text.ts:2:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/drawings/text.test.ts:4:1)

 FAIL  src/core/Drawings/__tests__/drawingTestUtils.ts
  ● Test suite failed to run

    Your test suite must contain at least one test.

      at onResult (node_modules/@jest/core/build/TestScheduler.js:133:18)
      at node_modules/@jest/core/build/TestScheduler.js:254:19
      at node_modules/emittery/index.js:363:13
          at Array.map (<anonymous>)
      at Emittery.emit (node_modules/emittery/index.js:361:23)

 FAIL  src/core/Drawings/__tests__/drawings/ruler.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { clamp } from 'lodash-es';
        | ^
      2 |
      3 | import type { Anchor, Bounds, ContainerSize, Point, SeriesApi } from './types';
      4 |

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/helpers.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/ruler/ruler.ts:10:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/drawings/ruler.test.ts:5:1)

 FAIL  src/core/Drawings/__tests__/shortcuts.test.ts
  ● 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:

    C:\Users\ShkinderDV\moex-chart\node_modules\lodash-es\lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { clamp } from 'lodash-es';
        | ^
      2 |
      3 | import type { Anchor, Bounds, ContainerSize, Point, SeriesApi } from './types';
      4 |

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/core/Drawings/helpers.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/axisLine/axisLine.ts:2:1)
      at Object.<anonymous> (src/core/Drawings/axisLine/index.ts:1:1)
      at Object.<anonymous> (src/constants/drawing.ts:1:1)
      at Object.<anonymous> (src/constants/index.ts:3:1)
      at Object.<anonymous> (src/core/Drawings/shortcuts.ts:1:1)
      at Object.<anonymous> (src/core/Drawings/__tests__/shortcuts.test.ts:1:1)


Test Suites: 18 failed, 7 passed, 25 total
Tests:       66 passed, 66 total
Snapshots:   0 total
Time:        23.244 s
Ran all test suites related to files matching /C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\SeriesDrawingBase.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\SeriesDrawingBase.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\drawingTestUtils.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\drawings\\CustomPriceAxis.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\drawings\\CustomTimeAxis.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\drawings\\axisLine.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\drawings\\diapson.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\drawings\\fibonacciRetracement.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\drawings\\line.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\drawings\\parallelChannel.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\drawings\\ray.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\drawings\\rectangle.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\drawings\\regressionTrend.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\drawings\\ruler.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\drawings\\sliderPosition.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\drawings\\text.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\drawings\\traectory.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\drawings\\volumeProfile.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\handles.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\helpers.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\shortcuts.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\__tests__\\utils.test.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\axis\\CustomPriceAxis.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\axis\\CustomTimeAxis.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\axisLine\\axisLine.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\axisLine\\paneRenderer.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\diapson\\diapson.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\diapson\\paneRenderer.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\fibonacciRetracement\\fibonacciRetracement.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\fibonacciRetracement\\paneRenderer.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\handles.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\helpers.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\line\\lineDrawing.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\line\\paneRenderer.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\parallelChannel\\paneRenderer.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\parallelChannel\\parallelChannel.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\ray\\paneRenderer.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\ray\\ray.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\rectangle\\paneRenderer.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\rectangle\\rectangle.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\regressionTrend\\paneRenderer.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\regressionTrend\\regressionTrend.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\sliderPosition\\paneRenderer.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\sliderPosition\\sliderPosition.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\traectory\\paneRenderer.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\traectory\\traectory.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\volumeProfile\\paneRenderer.ts|C:\\Users\\ShkinderDV\\moex-chart\\src\\core\\Drawings\\volumeProfile\\volumeProfile.ts/i.
husky - pre-commit script failed (code 1)
Больше возможностей при регистрации:
