Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps): bump json-parse-even-better-errors from 2.3.1 to 3.0.2 #18383

Closed
wants to merge 1 commit into from

chore(deps): bump json-parse-even-better-errors from 2.3.1 to 3.0.2

d505be7
Select commit
Loading
Failed to load commit list.
Closed

chore(deps): bump json-parse-even-better-errors from 2.3.1 to 3.0.2 #18383

chore(deps): bump json-parse-even-better-errors from 2.3.1 to 3.0.2
d505be7
Select commit
Loading
Failed to load commit list.
Azure Pipelines / webpack.webpack failed May 6, 2024 in 1h 59m 32s

Build #20240506.2 had test failures

12 errors / 11 warnings

Details

Tests

  • Failed: 29,196 (14.51%)
  • Passed: 170,511 (84.77%)
  • Other: 1,446 (0.72%)
  • Total: 201,153

Annotations

Check failure on line 1146866 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / webpack.webpack

Build log #L1146866 

Bash exited with code '1'.

Check failure on line 1149505 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / webpack.webpack

Build log #L1149505 

Cmd.exe exited with code '1'.

Check failure on line 222196 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / webpack.webpack

Build log #L222196 

The Operation will be canceled. The next steps may not contain expected logs.

Check failure on line 1 in warmup should warmup webpack

See this annotation in the file changed.

@azure-pipelines azure-pipelines / webpack.webpack

warmup should warmup webpack 

Test failed
Raw output 
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/vsts/work/1/s/node_modules/json-parse-even-better-errors/lib/index.js:107
    result[NEWLINE] = match[1] ?? DEFAULT_NEWLINE
                                ^

SyntaxError: Unexpected token ?
    at new Script (vm.js:83:7)
    at Runtime.createScriptFromCode (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1728:14)
    at Runtime._execModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1596:25)
    at Runtime._loadModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1185:12)
    at Runtime.requireModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1009:12)
    at Runtime.requireModuleOrMock (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1210:21)
    at Object.<anonymous> (/home/vsts/work/1/s/lib/Compiler.js:11599:27)
    at Runtime._execModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1646:24)
    at Runtime._loadModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1185:12)
    at Runtime.requireModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1009:12)
    at Runtime.requireModuleOrMock (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1210:21)
    at Object.<anonymous> (/home/vsts/work/1/s/lib/webpack.js:1652:26)
    at Runtime._execModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1646:24)
    at Runtime._loadModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1185:12)
    at Runtime.requireModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1009:12)
    at Runtime.requireModuleOrMock (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1210:21)
    at Object.<anonymous>.lazyFunction (/home/vsts/work/1/s/lib/index.js:5706:10)
    at /home/vsts/work/1/s/lib/util/memoize.js:283:16
    at f (/home/vsts/work/1/s/lib/index.js:5631:12)
    at Object.done (/home/vsts/work/1/s/test/helpers/warmup-webpack.js:5:3)
    at Promise (/home/vsts/work/1/s/node_modules/jest-circus/build/utils.js:381:26)
    at new Promise (<anonymous>)
    at callAsyncCircusFn (/home/vsts/work/1/s/node_modules/jest-circus/build/utils.js:316:10)
    at _callCircusTest (/home/vsts/work/1/s/node_modules/jest-circus/build/run.js:218:40)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Check failure on line 1 in ConfigTestCases additional-pass simple simple should compile

See this annotation in the file changed.

@azure-pipelines azure-pipelines / webpack.webpack

ConfigTestCases additional-pass simple simple should compile 

Test failed
Raw output 
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/vsts/work/1/s/node_modules/json-parse-even-better-errors/lib/index.js:107
    result[NEWLINE] = match[1] ?? DEFAULT_NEWLINE
                                ^

SyntaxError: Unexpected token ?
    at new Script (vm.js:83:7)
    at Runtime.createScriptFromCode (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1728:14)
    at Runtime._execModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1596:25)
    at Runtime._loadModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1185:12)
    at Runtime.requireModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1009:12)
    at Runtime.requireModuleOrMock (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1210:21)
    at Object.<anonymous> (/home/vsts/work/1/s/lib/Compiler.js:11599:27)
    at Runtime._execModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1646:24)
    at Runtime._loadModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1185:12)
    at Runtime.requireModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1009:12)
    at Runtime.requireModuleOrMock (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1210:21)
    at Object.<anonymous> (/home/vsts/work/1/s/lib/webpack.js:1652:26)
    at Runtime._execModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1646:24)
    at Runtime._loadModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1185:12)
    at Runtime.requireModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1009:12)
    at Runtime.requireModuleOrMock (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1210:21)
    at Object.<anonymous>.lazyFunction (/home/vsts/work/1/s/lib/index.js:5706:10)
    at /home/vsts/work/1/s/lib/util/memoize.js:283:16
    at f (/home/vsts/work/1/s/lib/index.js:5631:12)
    at Object.done (/home/vsts/work/1/s/test/ConfigTestCases.template.js:709:22)
    at Promise (/home/vsts/work/1/s/node_modules/jest-circus/build/utils.js:381:26)
    at new Promise (<anonymous>)
    at callAsyncCircusFn (/home/vsts/work/1/s/node_modules/jest-circus/build/utils.js:316:10)
    at _callCircusTest (/home/vsts/work/1/s/node_modules/jest-circus/build/run.js:218:40)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Check failure on line 1 in ConfigTestCases amd disabled disabled should compile

See this annotation in the file changed.

@azure-pipelines azure-pipelines / webpack.webpack

ConfigTestCases amd disabled disabled should compile 

Test failed
Raw output 
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/vsts/work/1/s/node_modules/json-parse-even-better-errors/lib/index.js:107
    result[NEWLINE] = match[1] ?? DEFAULT_NEWLINE
                                ^

SyntaxError: Unexpected token ?
    at new Script (vm.js:83:7)
    at Runtime.createScriptFromCode (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1728:14)
    at Runtime._execModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1596:25)
    at Runtime._loadModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1185:12)
    at Runtime.requireModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1009:12)
    at Runtime.requireModuleOrMock (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1210:21)
    at Object.<anonymous> (/home/vsts/work/1/s/lib/Compiler.js:11599:27)
    at Runtime._execModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1646:24)
    at Runtime._loadModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1185:12)
    at Runtime.requireModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1009:12)
    at Runtime.requireModuleOrMock (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1210:21)
    at Object.<anonymous> (/home/vsts/work/1/s/lib/webpack.js:1652:26)
    at Runtime._execModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1646:24)
    at Runtime._loadModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1185:12)
    at Runtime.requireModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1009:12)
    at Runtime.requireModuleOrMock (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1210:21)
    at Object.<anonymous>.lazyFunction (/home/vsts/work/1/s/lib/index.js:5706:10)
    at /home/vsts/work/1/s/lib/util/memoize.js:283:16
    at f (/home/vsts/work/1/s/lib/index.js:5631:12)
    at Object.done (/home/vsts/work/1/s/test/ConfigTestCases.template.js:709:22)
    at Promise (/home/vsts/work/1/s/node_modules/jest-circus/build/utils.js:381:26)
    at new Promise (<anonymous>)
    at callAsyncCircusFn (/home/vsts/work/1/s/node_modules/jest-circus/build/utils.js:316:10)
    at _callCircusTest (/home/vsts/work/1/s/node_modules/jest-circus/build/run.js:218:40)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Check failure on line 1 in ConfigTestCases asset-emitted normal normal should compile

See this annotation in the file changed.

@azure-pipelines azure-pipelines / webpack.webpack

ConfigTestCases asset-emitted normal normal should compile 

Test failed
Raw output 
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/vsts/work/1/s/node_modules/json-parse-even-better-errors/lib/index.js:107
    result[NEWLINE] = match[1] ?? DEFAULT_NEWLINE
                                ^

SyntaxError: Unexpected token ?
    at new Script (vm.js:83:7)
    at Runtime.createScriptFromCode (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1728:14)
    at Runtime._execModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1596:25)
    at Runtime._loadModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1185:12)
    at Runtime.requireModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1009:12)
    at Runtime.requireModuleOrMock (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1210:21)
    at Object.<anonymous> (/home/vsts/work/1/s/lib/Compiler.js:11599:27)
    at Runtime._execModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1646:24)
    at Runtime._loadModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1185:12)
    at Runtime.requireModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1009:12)
    at Runtime.requireModuleOrMock (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1210:21)
    at Object.<anonymous> (/home/vsts/work/1/s/lib/webpack.js:1652:26)
    at Runtime._execModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1646:24)
    at Runtime._loadModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1185:12)
    at Runtime.requireModule (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1009:12)
    at Runtime.requireModuleOrMock (/home/vsts/work/1/s/node_modules/jest-runtime/build/index.js:1210:21)
    at Object.<anonymous>.lazyFunction (/home/vsts/work/1/s/lib/index.js:5706:10)
    at /home/vsts/work/1/s/lib/util/memoize.js:283:16
    at f (/home/vsts/work/1/s/lib/index.js:5631:12)
    at Object.done (/home/vsts/work/1/s/test/ConfigTestCases.template.js:709:22)
    at Promise (/home/vsts/work/1/s/node_modules/jest-circus/build/utils.js:381:26)
    at new Promise (<anonymous>)
    at callAsyncCircusFn (/home/vsts/work/1/s/node_modules/jest-circus/build/utils.js:316:10)
    at _callCircusTest (/home/vsts/work/1/s/node_modules/jest-circus/build/run.js:218:40)
    at process._tickCallback (internal/process/next_tick.js:68:7)
View more details on Azure Pipelines