storyblok / richtext

A custom javascript resolver for the Storyblok Richtext field.
MIT License
9 stars 3 forks source link

chore(deps-dev): bump the linting-dx-tools group across 1 directory with 4 updates #52

Closed dependabot[bot] closed 4 months ago

dependabot[bot] commented 4 months ago

Bumps the linting-dx-tools group with 4 updates in the / directory: eslint-plugin-vue, lint-staged, prettier and @typescript-eslint/parser.

Updates eslint-plugin-vue from 9.26.0 to 9.27.0

Release notes

Sourced from eslint-plugin-vue's releases.

v9.27.0

✨ Enhancements

🐛 Bug Fixes

⚙️ Updates

Full Changelog: https://github.com/vuejs/eslint-plugin-vue/compare/v9.26.0...v9.27.0

Commits


Updates lint-staged from 15.2.4 to 15.2.7

Release notes

Sourced from lint-staged's releases.

v15.2.7

Patch Changes

  • #1440 a51be80 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version drops the --path-format=absolute option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading git to the latest version.

v15.2.6

Patch Changes

  • #1433 119adb2 Thanks @​iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.

v15.2.5

Patch Changes

  • #1424 31a1f95 Thanks @​iiroj! - Allow approximately equivalent versions of direct dependencies by using the "~" character in the version ranges. This means a more recent patch version of a dependency is allowed if available.

  • #1423 91abea0 Thanks @​iiroj! - Improve error logging when failing to read or parse a configuration file

  • #1424 ee43f15 Thanks @​iiroj! - Upgrade micromatch@4.0.7

Changelog

Sourced from lint-staged's changelog.

15.2.7

Patch Changes

  • #1440 a51be80 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version drops the --path-format=absolute option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading git to the latest version.

15.2.6

Patch Changes

  • #1433 119adb2 Thanks @​iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.

15.2.5

Patch Changes

  • #1424 31a1f95 Thanks @​iiroj! - Allow approximately equivalent versions of direct dependencies by using the "~" character in the version ranges. This means a more recent patch version of a dependency is allowed if available.

  • #1423 91abea0 Thanks @​iiroj! - Improve error logging when failing to read or parse a configuration file

  • #1424 ee43f15 Thanks @​iiroj! - Upgrade micromatch@4.0.7

Commits
  • 87e4b30 chore(changeset): release (#1441)
  • a39e829 docs: adjust changeset
  • a51be80 fix: drop option to support earlier Git versions
  • a91d942 chore(changeset): release
  • 119adb2 fix: use native git command to get .git directory
  • e0386dc fix: use native git command to get top-level directory for repo
  • 6593870 ci: test Node.js versions against current instead of latest dependency
  • 6c226c5 ci: add workflow for testing required Node.js semver range
  • f7e4106 chore(changeset): release
  • fc75303 build(release): lower next version bump from minor to patch
  • Additional commits viewable in compare view


Updates prettier from 3.2.5 to 3.3.3

Release notes

Sourced from prettier's releases.

3.3.3

🔗 Changelog

3.3.2

🔗 Changelog

3.3.1

🔗 Changelog

3.3.0

diff

🔗 Release note

Changelog

Sourced from prettier's changelog.

3.3.3

diff

Add parentheses for nullish coalescing in ternary (#16391 by @​cdignam-segment)

This change adds clarity to operator precedence.

// Input
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.2
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.3
foo ? (bar ?? foo) : baz;
(foo ?? bar) ? a : b;
a ? b : (foo ?? bar);

Add parentheses for decorator expressions (#16458 by @​y-schneider)

Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.

// Input
@(foo`tagged template`)
class X {}

// Prettier 3.3.2
@​footagged template
class X {}

// Prettier 3.3.3
@(footagged template)
class X {}

Support @let declaration syntax (#16474 by @​sosukesuzuki)

Adds support for Angular v18 @let declaration syntax.

Please see the following code example. The @let declaration allows you to define local variables within the template:

... (truncated)

Commits


Updates @typescript-eslint/parser from 7.2.0 to 7.16.0

Release notes

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

v7.16.0

7.16.0 (2024-07-08)

🚀 Features

  • ast-spec: add parent property to AccessorProperty node types (#9487)
  • eslint-plugin: [no-unnecessary-type-parameters] port from v8 to v7 (#9473)
  • eslint-plugin: [no-unnecessary-parameter-property-assignment] add new rule (#8903)
  • eslint-plugin: add support for nested namespaces to unsafe-member-access (#9478)
  • eslint-plugin: [no-floating-promises] add checkThenables option (#9263)
  • rule-tester: stricter rule test validations (#9086)

🩹 Fixes

  • deps: update dependency @​eslint-community/regexpp to v4.11.0 (#9497)
  • eslint-plugin: [no-floating-promises] add suggestions to tests from #9263 checkThenables (#9515, #9263)
  • eslint-plugin: [restrict-template-expressions] don't report tuples if allowArray option is enabled (#9492)
  • utils: context.parserPath may be undefined (#9486)
  • website: react key error on internal pages of website (#9506)

❤️ Thank You

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

v7.15.0

7.15.0 (2024-07-01)

🚀 Features

  • eslint-plugin: [array-type] detect Readonly<string[]> case (#8752)
  • eslint-plugin: back-port new rules around empty object types from v8 (#9443)

🩹 Fixes

  • disable EXPERIMENTAL_useProjectService in disabled-type-checked shared config (#9459)
  • eslint-plugin: [no-unsafe-return] differentiate a types-error any from a true any (#9254)
  • eslint-plugin: [no-unsafe-call] differentiate a types-error any from a true any (#9304)
  • utils: clean outdated RuleTester export (#9322)

❤️ Thank You

... (truncated)

Changelog

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

7.16.0 (2024-07-08)

🩹 Fixes

  • deps: update dependency @​eslint-community/regexpp to v4.11.0

  • website: react key error on internal pages of website

❤️ Thank You

  • Abraham Guo
  • auvred
  • Josh Goldberg ✨
  • Juan Sanchez
  • Vinccool96
  • YeonJuan
  • Yukihiro Hasegawa

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

7.15.0 (2024-07-01)

This was a version bump only for parser to align it with other projects, there were no code changes.

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

7.14.1 (2024-06-24)

This was a version bump only for parser to align it with other projects, there were no code changes.

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

7.14.0 (2024-06-24)

🚀 Features

  • support TypeScript 5.5

❤️ Thank You

  • Brad Zacher
  • cm-ayf
  • Jake Bailey
  • James Zhan
  • Joshua Chen
  • yoshi2no

... (truncated)

Commits
  • e803c50 chore(release): publish 7.16.0
  • 2865d31 chore(release): publish 7.15.0
  • b4fe94f chore(release): publish 7.14.1
  • dfc4469 chore(release): publish 7.14.0
  • 1212a8f chore(release): publish 7.13.1
  • 8a178ed chore(release): publish 7.13.0
  • c9a6dd9 feat(parser, typescript-estree): export withoutProjectParserOptions utility (...
  • 7e93b28 chore(release): publish 7.12.0
  • 2bbf656 fix(types): correct typing ParserOptions (#9202)
  • e360541 chore(release): publish 7.11.0
  • 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 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
dependabot[bot] commented 4 months ago

Superseded by #53.