npm(deps-dev): bump typescript from 5.5.4 to 5.7.2 #239

dependabot · 2024-12-01T05:40:42Z

Bumps typescript from 5.5.4 to 5.7.2.

Release notes

TypeScript 5.7

For release notes, check out the release announcement.

fixed issues query for Typescript 5.7.0 (Beta).

fixed issues query for Typescript 5.7.1 (RC).

fixed issues query for Typescript 5.7.2 (Stable).

Downloads are available on:

npm

TypeScript 5.7 RC

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

fixed issues query for Typescript 5.7.0 (Beta).

fixed issues query for Typescript 5.7.1 (RC).

Downloads are available on:

npm

TypeScript 5.7 Beta

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

fixed issues query for Typescript 5.7.0 (Beta).

Downloads are available on:

npm

TypeScript 5.6.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

fixed issues query for Typescript 5.6.0 (Beta).

fixed issues query for Typescript 5.6.1 (RC).

fixed issues query for Typescript 5.6.2 (Stable).

fixed issues query for Typescript 5.6.3 (Stable).

Downloads are available on:

npm

NuGet package

... (truncated)

Commits

d701d90 Bump version to 5.7.2 and LKG
0503a63 🤖 Pick PR #60450 (Move to file: fix detection of refe...) into release-5.7 (#...
3140dbb 🤖 Pick PR #60488 (Stub out copilotRelated command) into release-5.7 (#60495)
c1216de Update LKG
3ee2b95 🤖 Pick PR #60415 (Fix false positive rewriteRelativeI...) into release-5.7 (#...
44bd3f2 Bump version to 5.7.1-rc and LKG
5925c81 Update LKG
84d58cf Merge remote-tracking branch 'origin/main' into release-5.7
0ec4d30 Fixing exception on unsaved file (#60362)
11b2930 Add compatible overloads that accept ArrayBuffer to BigInt64Array/BigUint64Ar...
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [typescript](https://github.com/microsoft/TypeScript) from 5.5.4 to 5.7.2. - [Release notes](https://github.com/microsoft/TypeScript/releases) - [Changelog](https://github.com/microsoft/TypeScript/blob/main/azure-pipelines.release.yml) - [Commits](microsoft/TypeScript@v5.5.4...v5.7.2) --- updated-dependencies: - dependency-name: typescript dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>

github-actions · 2024-12-01T05:43:46Z

Coverage report

Caution

Coverage does not meet threshold
Statements coverage not met for global: expected >=100%, but got 30.489073881373567%

St.^❔	Category	Percentage	Covered / Total
🔴	Statements	30.49% (-69.51% 🔻)	293/961
🟢	Branches	89.19% (-10.81% 🔻)	33/37
🔴	Functions	52.94% (-47.06% 🔻)	9/17
🔴	Lines	30.49% (-69.51% 🔻)	293/961

Show files with reduced coverage 🔻

St.^❔	File	Statements	Branches	Functions	Lines
🔴	`...` / postbuild.mjs	0% (-100% 🔻)	0% (-100% 🔻)	0% (-100% 🔻)	0% (-100% 🔻)
🔴	`...` / convert.ts	0% (-100% 🔻)	0% (-100% 🔻)	0% (-100% 🔻)	0% (-100% 🔻)
🔴	`...` / init.ts	0% (-100% 🔻)	0% (-100% 🔻)	0% (-100% 🔻)	0% (-100% 🔻)
🟢	src/messages.ts	92.42% (-7.58% 🔻)	100%	20% (-80% 🔻)	92.42% (-7.58% 🔻)
🔴	src/utils.ts	0% (-100% 🔻)	0% (-100% 🔻)	0% (-100% 🔻)	0% (-100% 🔻)

Test suite run failed

Failed tests: 0/21. Failed suites: 4/9.

  ● 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/csv2gsheets/csv2gsheets/node_modules/inquirer/lib/index.js:6
    import { default as List } from './prompts/list.js';
    ^^^^^^

    SyntaxError: Cannot use import statement outside a module

       7 | import { C2gError } from '../src/c2g-error';
       8 | import * as constants from '../src/constants';
    >  9 | import inquirer from 'inquirer';
         | ^
      10 | import { MESSAGES } from '../src/messages';
      11 | import * as utils from '../src/utils';
      12 |

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (test/utils.test.ts: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/csv2gsheets/csv2gsheets/node_modules/inquirer/lib/index.js:6
    import { default as List } from './prompts/list.js';
    ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      3 | import fs from 'fs';
      4 | import { drive_v3 } from 'googleapis';
    > 5 | import inquirer, { QuestionCollection } from 'inquirer';
        | ^
      6 | import path from 'path';
      7 |
      8 | import { Config, CONFIG_FILE_NAME, DEFAULT_CONFIG } from './constants';

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/utils.ts:5:1)
      at Object.<anonymous> (src/commands/convert.ts:17:1)
      at Object.<anonymous> (test/convert.test.ts:12: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/csv2gsheets/csv2gsheets/postbuild/postbuild.mjs:5
    import fs from 'fs';
    ^^^^^^

    SyntaxError: Cannot use import statement outside a module

    > 1 | import * as postbuild from '../postbuild/postbuild.mjs';
        | ^
      2 |
      3 | import fs from 'fs';
      4 | import path from 'path';

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (test/postbuild.test.ts:1: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/csv2gsheets/csv2gsheets/node_modules/inquirer/lib/index.js:6
    import { default as List } from './prompts/list.js';
    ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      2 |
      3 | import fs from 'fs';
    > 4 | import inquirer from 'inquirer';
        | ^
      5 |
      6 | import * as auth from '../src/auth';
      7 | import login from '../src/commands/login';

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (test/init.test.ts:4:1)

Report generated by 🧪jest coverage report action from 686684f

dependabot · 2025-02-01T05:09:11Z

Superseded by #248.

dependabot bot requested a review from ttsukagoshi as a code owner December 1, 2024 05:40

dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Dec 1, 2024

dependabot bot assigned ttsukagoshi Dec 1, 2024

dependabot bot mentioned this pull request Dec 1, 2024

npm(deps-dev): bump typescript from 5.5.4 to 5.6.3 #229

Closed

dependabot bot closed this Feb 1, 2025

dependabot bot deleted the dependabot/npm_and_yarn/main/typescript-5.7.2 branch February 1, 2025 05:09

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

npm(deps-dev): bump typescript from 5.5.4 to 5.7.2 #239

npm(deps-dev): bump typescript from 5.5.4 to 5.7.2 #239

dependabot bot commented on behalf of github Dec 1, 2024

github-actions bot commented Dec 1, 2024

dependabot bot commented on behalf of github Feb 1, 2025

npm(deps-dev): bump typescript from 5.5.4 to 5.7.2 #239

npm(deps-dev): bump typescript from 5.5.4 to 5.7.2 #239

Conversation

dependabot bot commented on behalf of github Dec 1, 2024

TypeScript 5.7

TypeScript 5.7 RC

TypeScript 5.7 Beta

TypeScript 5.6.3

github-actions bot commented Dec 1, 2024

Coverage report

Test suite run failed

dependabot bot commented on behalf of github Feb 1, 2025