search

swiftlang / vscode-swift

Visual Studio Code Extension for Swift
https://marketplace.visualstudio.com/items?itemName=sswg.swift-lang
Apache License 2.0
705 stars 47 forks source link

Bump the all-dependencies group across 1 directory with 5 updates #900

Closed dependabot[bot] closed 2 weeks ago

dependabot[bot] commented 2 weeks ago

Bumps the all-dependencies group with 5 updates in the / directory:

Package From To
@typescript-eslint/eslint-plugin 7.12.0 7.13.0
@typescript-eslint/parser 7.12.0 7.13.0
c8 10.1.1 10.1.2
esbuild 0.21.4 0.21.5
prettier 3.3.1 3.3.2

Updates @typescript-eslint/eslint-plugin from 7.12.0 to 7.13.0

Release notes

Sourced from @​typescript-eslint/eslint-plugin's releases.

v7.13.0

7.13.0 (2024-06-10)

🚀 Features

  • eslint-plugin: [no-dynamic-delete] allow all string literals as index (#9280)
  • parser, typescript-estree: export withoutProjectParserOptions utility (#9233)
  • typescript-estree: require import = require() argument to be a string literal (#9226)
  • typescript-estree: forbid .body, .async, .generator on declare function (#9225)

🩹 Fixes

  • ast-spec: function-call-like callee should be Expression not LeftHandSideExpression (#9231)
  • eslint-plugin: [init-declarations] refine report locations (#8893)
  • eslint-plugin: [no-base-to-string] make error message more nuanced (#9281)
  • eslint-plugin: [no-unsafe-assignment] be more specific about error types (#8304)
  • eslint-plugin: [no-magic-numbers] fix implementation of the ignore option (#9167)
  • scope-manager: handle index signature in class (#9054)

❤️ Thank You

You can read about our versioning strategy and releases on our website.

Changelog

Sourced from @​typescript-eslint/eslint-plugin's changelog.

7.13.0 (2024-06-10)

🚀 Features

  • typescript-estree: require import = require() argument to be a string literal

  • typescript-estree: forbid .body, .async, .generator on declare function

  • eslint-plugin: [no-dynamic-delete] allow all string literals as index

🩹 Fixes

  • ast-spec: function-call-like callee should be Expression not LeftHandSideExpression

  • scope-manager: handle index signature in class

  • eslint-plugin: [init-declarations] refine report locations

  • eslint-plugin: [no-base-to-string] make error message more nuanced

  • eslint-plugin: [no-unsafe-assignment] be more specific about error types

  • eslint-plugin: [no-magic-numbers] fix implementation of the ignore option

❤️ Thank You

  • Fotis Papadogeorgopoulos
  • Joshua Chen
  • Kirk Waiblinger
  • Tobiloba Adedeji
  • Vinccool96
  • YeonJuan

You can read about our versioning strategy and releases on our website.

Commits
  • 8a178ed chore(release): publish 7.13.0
  • 63e53e2 chore(deps): update dependency prettier to v3.3.1 (#9308)
  • fb52f78 feat(eslint-plugin): [no-dynamic-delete] allow all string literals as index (...
  • ab2916c chore: enable eslint-plugin/no-property-in-node internally (#9261)
  • 629035f docs: mention rule scripts under Local Development (#9258)
  • bf5394d fix(eslint-plugin): [no-magic-numbers] fix implementation of the ignore opt...
  • 60fb643 chore(deps): update dependency prettier to v3.3.0 (#9266)
  • c6e9719 docs(eslint-plugin): [sort-type-constituents] deprecate the rule (#9253)
  • 293fb24 fix(eslint-plugin): [no-unsafe-assignment] be more specific about error types...
  • cb1720d fix(eslint-plugin): [no-base-to-string] make error message more nuanced (#9281)
  • Additional commits viewable in compare view


Updates @typescript-eslint/parser from 7.12.0 to 7.13.0

Release notes

Sourced from @​typescript-eslint/parser's releases.

v7.13.0

7.13.0 (2024-06-10)

🚀 Features

  • eslint-plugin: [no-dynamic-delete] allow all string literals as index (#9280)
  • parser, typescript-estree: export withoutProjectParserOptions utility (#9233)
  • typescript-estree: require import = require() argument to be a string literal (#9226)
  • typescript-estree: forbid .body, .async, .generator on declare function (#9225)

🩹 Fixes

  • ast-spec: function-call-like callee should be Expression not LeftHandSideExpression (#9231)
  • eslint-plugin: [init-declarations] refine report locations (#8893)
  • eslint-plugin: [no-base-to-string] make error message more nuanced (#9281)
  • eslint-plugin: [no-unsafe-assignment] be more specific about error types (#8304)
  • eslint-plugin: [no-magic-numbers] fix implementation of the ignore option (#9167)
  • scope-manager: handle index signature in class (#9054)

❤️ Thank You

You can read about our versioning strategy and releases on our website.

Changelog

Sourced from @​typescript-eslint/parser's changelog.

7.13.0 (2024-06-10)

🚀 Features

  • parser, typescript-estree: export withoutProjectParserOptions utility

❤️ Thank You

  • Fotis Papadogeorgopoulos
  • Joshua Chen
  • Kirk Waiblinger
  • Tobiloba Adedeji
  • Vinccool96
  • YeonJuan

You can read about our versioning strategy and releases on our website.

Commits
  • 8a178ed chore(release): publish 7.13.0
  • c9a6dd9 feat(parser, typescript-estree): export withoutProjectParserOptions utility (...
  • See full diff in compare view


Updates c8 from 10.1.1 to 10.1.2

Release notes

Sourced from c8's releases.

v10.1.2

10.1.2 (2024-06-13)

Bug Fixes

  • deps: make monocart-coverage-reports an optional with meta defined (3b91fda)
Changelog

Sourced from c8's changelog.

10.1.2 (2024-06-13)

Bug Fixes

  • deps: make monocart-coverage-reports an optional with meta defined (3b91fda)
Commits
  • ff146b4 chore(main): release 10.1.2 (#538)
  • 3b91fda fix(deps): make monocart-coverage-reports an optional with meta defined
  • See full diff in compare view


Updates esbuild from 0.21.4 to 0.21.5

Release notes

Sourced from esbuild's releases.

v0.21.5

  • Fix Symbol.metadata on classes without a class decorator (#3781)

    This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

  • Allow unknown import attributes to be used with the copy loader (#3792)

    Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

    // This is an error with "--bundle" without also using "--external:./bagel.js"
import tasty from "./bagel.js" with { type: "bagel" }

    Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

    However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

    // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
import tasty from "./tasty.bagel" with { type: "bagel" }

  • Support import attributes with glob-style imports (#3797)

    This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

    async function loadLocale(locale: string): Locale {
  const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
  return unpackLocale(locale, data)
}

    Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

    ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data

    example.ts:2:28:
  2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
    ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~

    In addition, this change means plugins can now access the contents of with for glob-style imports.

  • Support ${configDir} in tsconfig.json files (#3782)

    This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.21.5

  • Fix Symbol.metadata on classes without a class decorator (#3781)

    This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

  • Allow unknown import attributes to be used with the copy loader (#3792)

    Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

    // This is an error with "--bundle" without also using "--external:./bagel.js"
import tasty from "./bagel.js" with { type: "bagel" }

    Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

    However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

    // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
import tasty from "./tasty.bagel" with { type: "bagel" }

  • Support import attributes with glob-style imports (#3797)

    This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

    async function loadLocale(locale: string): Locale {
  const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
  return unpackLocale(locale, data)
}

    Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

    ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data

    example.ts:2:28:
  2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
    ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~

    In addition, this change means plugins can now access the contents of with for glob-style imports.

  • Support ${configDir} in tsconfig.json files (#3782)

    This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

... (truncated)

Commits


Updates prettier from 3.3.1 to 3.3.2

Release notes

Sourced from prettier's releases.

3.3.2

🔗 Changelog

Changelog

Sourced from prettier's changelog.

3.3.2

diff

Fix handlebars path expressions starts with @ (#16358 by @​Princeyadav05)

{{! Input }}
<div>{{@x.y.z}}</div>

{{! Prettier 3.3.1 }}
<div>{{@​x}}</div>


{{! Prettier 3.3.2 }}
<div>{{@​x.y.z}}</div>

Commits


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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions