Skip to content

chore(deps): update code style deps #55

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
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore(deps): update code style deps #55

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 25, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint (source) 8.52.0 -> 8.57.1 age adoption passing confidence
lint-staged 15.2.2 -> 15.5.1 age adoption passing confidence
prettier (source) 3.2.5 -> 3.5.3 age adoption passing confidence

Release Notes

eslint/eslint (eslint)

v8.57.1

Compare Source

Bug Fixes
  • a19072f fix: add logic to handle fixTypes in the lintText() method (#​18900) (Francesco Trotta)
  • 04c7188 fix: Don't lint same file multiple times (#​18899) (Francesco Trotta)
  • 87ec3c4 fix: do not throw when defining a global named __defineSetter__ (#​18898) (Francesco Trotta)
  • 60a1267 fix: Provide helpful error message for nullish configs (#​18889) (Milos Djermanovic)
  • a0dea8e fix: allow name in global ignores, fix --no-ignore for non-global (#​18875) (Milos Djermanovic)
  • 3836bb4 fix: do not crash on error in fs.walk filter (#​18886) (Milos Djermanovic)
  • 2dec349 fix: skip processor code blocks that match only universal patterns (#​18880) (Milos Djermanovic)
Documentation
Build Related
  • 35d366a build: Support updates to previous major versions (#​18870) (Milos Djermanovic)
Chores

v8.57.0

Compare Source

Features
  • 1120b9b feat: Add loadESLint() API method for v8 (#​18098) (Nicholas C. Zakas)
  • dca7d0f feat: Enable eslint.config.mjs and eslint.config.cjs (#​18066) (Nitin Kumar)
Bug Fixes
  • 2196d97 fix: handle absolute file paths in FlatRuleTester (#​18064) (Nitin Kumar)
  • 69dd1d1 fix: Ensure config keys are printed for config errors (#​18067) (Nitin Kumar)
  • 9852a31 fix: deep merge behavior in flat config (#​18065) (Nitin Kumar)
  • 4c7e9b0 fix: allow circular references in config (#​18056) (Milos Djermanovic)
Documentation
Chores

v8.56.0

Compare Source

Features
  • 0dd9704 feat: Support custom severity when reporting unused disable directives (#​17212) (Bryan Mishkin)
  • 31a7e3f feat: fix no-restricted-properties false negatives with unknown objects (#​17818) (Arka Pratim Chaudhuri)
Bug Fixes
  • 7d5e5f6 fix: TypeError: fs.exists is not a function on read-only file system (#​17846) (Francesco Trotta)
  • 74739c8 fix: suggestion with invalid syntax in no-promise-executor-return rule (#​17812) (Bryan Mishkin)
Documentation
  • 9007719 docs: update link in ways-to-extend.md (#​17839) (Amel SELMANE)
  • 3a22236 docs: Update README (GitHub Actions Bot)
  • 54c3ca6 docs: fix migration-guide example (#​17829) (Tanuj Kanti)
  • 4391b71 docs: check config comments in rule examples (#​17815) (Francesco Trotta)
  • fd28363 docs: remove mention about ESLint stylistic rules in readme (#​17810) (Zwyx)
  • 48ed5a6 docs: Update README (GitHub Actions Bot)
Chores

v8.55.0

Compare Source

Features
  • 8c9e6c1 feat: importNamePattern option in no-restricted-imports (#​17721) (Tanuj Kanti)
Documentation
  • 83ece2a docs: fix typo --rules -> --rule (#​17806) (OKURA Masafumi)
  • fffca5c docs: remove "Open in Playground" buttons for removed rules (#​17791) (Francesco Trotta)
  • a6d9442 docs: fix correct/incorrect examples of rules (#​17789) (Tanuj Kanti)
  • 383e999 docs: update and fix examples for no-unused-vars (#​17788) (Tanuj Kanti)
  • 5a8efd5 docs: add specific stylistic rule for each deprecated rule (#​17778) (Etienne)
Chores

v8.54.0

Compare Source

Features
  • a7a883b feat: for-direction rule add check for condition in reverse order (#​17755) (Angelo Annunziata)
  • 1452dc9 feat: Add suggestions to no-console (#​17680) (Joel Mathew Koshy)
  • 21ebf8a feat: update no-array-constructor rule (#​17711) (Francesco Trotta)
Bug Fixes
  • 98926e6 fix: Ensure that extra data is not accidentally stored in the cache file (#​17760) (Milos Djermanovic)
  • e8cf9f6 fix: Make dark scroll bar in dark theme (#​17753) (Pavel)
  • 3cbeaad fix: Use cwd constructor option as config basePath in Linter (#​17705) (Milos Djermanovic)
Documentation
  • becfdd3 docs: Make clear when rules are removed (#​17728) (Nicholas C. Zakas)
  • 05d6e99 docs: update "Submit a Pull Request" page (#​17712) (Francesco Trotta)
  • eb2279e docs: display info about deprecated rules (#​17749) (Percy Ma)
  • d245326 docs: Correct working in migrating plugin docs (#​17722) (Filip Tammergård)
Chores

v8.53.0

Compare Source

Features

  • 528e1c0 feat: Deprecate formatting rules (#​17696) (Nicholas C. Zakas)
  • c0b11dd feat: Add suggestions for no-prototype-builtins (#​17677) (Yonathan Randolph)

Bug Fixes

  • 1ad6257 fix: ensure that exit code for fatal errors is not overwritten (#​17683) (Milos Djermanovic)
  • b329ea7 fix: add ; after JSX nodes in no-object-constructor autofix (#​17672) (Francesco Trotta)

Documentation

  • ab8c60d docs: change position of return to top button (#​17688) (Tanuj Kanti)
  • 4fc44c0 docs: update twitter icon to new X icon (#​17687) (Tanuj Kanti)
  • 4164b2c docs: Update README (GitHub Actions Bot)
  • 8651895 docs: Fix tabs in rule examples (#​17653) (Francesco Trotta)
  • 3aec1c5 docs: explained rule fixers and suggestions (#​17657) (Josh Goldberg ✨)

Chores

lint-staged/lint-staged (lint-staged)

v15.5.1

Compare Source

Patch Changes

  • #​1533 5d53534 Thanks @​iiroj! - Improve listing of staged files so that lint-staged doesn't crash when encountering an uninitialized submodule. This should result in less errors like:

    ✖ Failed to get staged files!

v15.5.0

Compare Source

Minor Changes
  • #​1526 630af5f Thanks @​iiroj! - Lint-staged no longer resets to the original state when preventing an empty git commit. This happens when your configured tasks reset all the staged changes, typically when trying to commit formatting changes which conflict with your linter setup like ESLint or Prettier.
Example with Prettier

By default Prettier prefers double quotes.

Previously
  1. Stage file.js with only double quotes " changed to '
  2. Run git commit -am "I don't like double quotes"
  3. Lint-staged runs prettier --write file.js, converting all the ' back to "
  4. Because there are now no changes, lint-staged fails, cancels the commit, and resets back to the original state
  5. Commit was not done, original state is restored and single quotes ' are staged
Now
  1. Stage file.js with only double-quotes " changed to '
  2. Run git commit -am "I don't like double quotes"
  3. Lint-staged runs prettier --write file.js, converting all the ' back to "
  4. Because there are now no changes, lint-staged fails and cancels the commit
  5. Commit was not done, and there are no staged changes

v15.4.3

Compare Source

Patch Changes
  • #​1512 cbfed1d Thanks @​tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.

v15.4.2

Compare Source

Patch Changes
  • #​1509 8827ebf Thanks @​iiroj! - Change lint-staged's dependencies to use caret (^) ranges instead of tilde (~). This makes it easier for package managers to perform dependency management when minor-level updates are also permitted instead of just patch-level.

v15.4.1

Compare Source

Patch Changes

v15.4.0

Compare Source

Minor Changes

  • #​1500 a8ec1dd Thanks @​iiroj! - Lint-staged now provides TypeScript types for the configuration and main Node.js API. You can use the JSDoc syntax in your JS configuration files:

    /**
 * @​filename: lint-staged.config.js
 * @​type {import('lint-staged').Configuration}
 */
export default {
  '*': 'prettier --write',
}

    It's also possible to use the .ts file extension for the configuration if your Node.js version supports it. The --experimental-strip-types flag was introduced in Node.js v22.6.0 and unflagged in v23.6.0, enabling Node.js to execute TypeScript files without additional configuration.

    export NODE_OPTIONS="--experimental-strip-types"

npx lint-staged --config lint-staged.config.ts
Patch Changes

v15.3.0

Compare Source

Minor Changes

  • #​1495 e69da9e Thanks @​iiroj! - Added more info to the debug logs so that "environment" info doesn't need to be added separately to GitHub issues.

  • #​1493 fa0fe98 Thanks @​iiroj! - Added more help messages around the automatic git stash that lint-staged creates as a backup (by default). The console output also displays the short git hash of the stash so that it's easier to recover lost files in case some fatal errors are encountered, or the process is killed before completing.

    For example:

    % npx lint-staged
✔ Backed up original state in git stash (20addf8)
✔ Running tasks for staged files...
✔ Applying modifications from tasks...
✔ Cleaning up temporary files...

    where the backup can be seen with git show 20addf8, or git stash list:

    % git stash list
stash@{0}: lint-staged automatic backup (20addf8)

v15.2.11

Compare Source

Patch Changes

  • #​1484 bcfe309 Thanks @​wormsik! - Escape paths containing spaces when using the "shell" option.

  • #​1487 7dd8caa Thanks @​iiroj! - Do not treat submodule root paths as "staged files". This caused lint-staged to fail to a Git error when only updating the revision of a submodule.

v15.2.10

Compare Source

Patch Changes

v15.2.9

Compare Source

Patch Changes
  • #​1463 b69ce2d Thanks @​iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warning MaxListenersExceededWarning: Possible EventEmitter memory leak detected.

v15.2.8

Compare Source

Patch Changes

  • f0480f0 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 switched the --show-toplevel flag with --show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.js child_process. The new flag returns a path relative to the working directory, avoiding the issue.

    The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.

v15.2.7

Compare Source

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

Compare Source

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

Compare Source

Patch Changes

v15.2.4

Compare Source

Patch Changes
  • 4f4537a Thanks @​iiroj! - Fix release issue with previous version; update dependencies
prettier/prettier (prettier)

v3.5.3

Compare Source

v3.5.2

Compare Source

diff

Remove module-sync condition (#​17156 by @​fisker)

In Prettier 3.5.0, we added module-sync condition to package.json, so that require("prettier") can use ESM version, but turns out it doesn't work if CommonJS and ESM plugins both imports builtin plugins. To solve this problem, we decide simply remove the module-sync condition, so require("prettier") will still use the CommonJS version, we'll revisit until require(ESM) feature is more stable.

v3.5.1

Compare Source

diff

Fix CLI crash when cache for old version exists (#​17100 by @​sosukesuzuki)

Prettier 3.5 uses a different cache format than previous versions, Prettier 3.5.0 crashes when reading existing cache file, Prettier 3.5.1 fixed the problem.

Support dockercompose and github-actions-workflow in VSCode (#​17101 by @​remcohaszing)

Prettier now supports the dockercompose and github-actions-workflow languages in Visual Studio Code.

v3.5.0

Compare Source

diff

🔗 Release Notes

v3.4.2

Compare Source

diff

Treat U+30A0 & U+30FB in Katakana Block as CJK (#​16796 by @​tats-u)

Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.

<!-- Input (--prose-wrap=never) -->

C言
語
・
C++
・
Go
・
Rust

<!-- Prettier 3.4.1 -->
C言語・ C++ ・ Go ・ Rust

<!-- Prettier 3.4.2 -->
C言語・C++・Go・Rust

U+30A0 can be used as the replacement of the - in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン＝サーンス”).

Fix comments print on class methods with decorators (#​16891 by @​fisker)
// Input
class A {
  @&#8203;decorator
  /** 
   * The method description
   *
  */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.1
class A {
  @&#8203;decorator
  async /**
   * The method description
   *
   */
  method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.2
class A {
  @&#8203;decorator
  /**
   * The method description
   *
   */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}
Fix non-idempotent formatting (#​16899 by @​seiyab)

This bug fix is not language-specific. You may see similar change in any languages. This fixes regression in 3.4.0 so change caused by it should yield same formatting as 3.3.3.

// Input
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.1 (first)
<div>
  foo
  <span>
    longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo
  </span>, abc
</div>;

// Prettier 3.4.1 (second)
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.2
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

v3.4.1

Compare Source

diff

Remove unnecessary parentheses around assignment in v-on (#​16887 by @​fisker)
<!-- Input -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

<!-- Prettier 3.4.0 -->
<template>
  <button @&#8203;click="(foo += 2)">Click</button>
</template>

<!-- Prettier 3.4.1 -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

v3.4.0

Compare Source

diff

🔗 Release Notes

v3.3.3

Compare Source

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
@&#8203;(foo`tagged template`)
class X {}

// Prettier 3.3.2
@&#8203;foo`tagged template`
class X {}

// Prettier 3.3.3
@&#8203;(foo`tagged 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:

@&#8203;let name = 'Frodo';

<h1>Dashboard for {{name}}</h1>
Hello, {{name}}

For more details, please refer to the excellent blog post by the Angular Team: Introducing @​let in Angular.

We also appreciate the Angular Team for kindly answering our questions to implement this feature.

v3.3.2

Compare Source

diff

Fix handlebars path expressions starts with @ (#​16358 by @​Princeyadav05)
{{! Input }}
<div>{{@&#8203;x.y.z}}</div>

{{! Prettier 3.3.1 }}
<div>{{@&#8203;x}}</div>

{{! Prettier 3.3.2 }}
<div>{{@&#8203;x.y.z}}</div>

v3.3.1

Compare Source

diff

Preserve empty lines in front matter (#​16347 by @​fisker)
<!-- Input -->
---
foo:
  - bar1

  - bar2

  - bar3
---
Markdown

<!-- Prettier 3.3.0 -->

---
foo:
  - bar1
  - bar2
  - bar3
---

Markdown

<!-- Prettier 3.3.1 -->
---
foo:
  - bar1

  - bar2

  - bar3
---

Markdown
Preserve explicit language in front matter (#​16348 by @​fisker)
<!-- Input -->
---yaml
title: Hello
slug: home
---

<!-- Prettier 3.3.0 -->
---
title: Hello
slug: home
---

<!-- Prettier 3.3.1 -->
---yaml
title: Hello
slug: home
---
Avoid line breaks in import attributes (#​16349 by @​fisker)
// Input
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };

// Prettier 3.3.0
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type:
  "json" };

// Prettier 3.3.1
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };

v3.3.0

Compare Source

diff

🔗 Release Notes

Configuration

📅 Schedule: Branch creation - "* 0-10 * * *" in timezone Europe/Kiev, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the frontend label Apr 25, 2024
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Apr 25, 2024

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

@renovate renovate bot force-pushed the renovate/code-style-deps branch from b8c2245 to 435ae7d Compare May 22, 2024 21:51
@renovate renovate bot changed the title chore(deps): update dependency eslint to v8.57.0 chore(deps): update code style deps May 22, 2024
@renovate renovate bot force-pushed the renovate/code-style-deps branch 2 times, most recently from 9df63ec to 3041271 Compare June 1, 2024 21:29
@renovate renovate bot force-pushed the renovate/code-style-deps branch 2 times, most recently from c77a388 to bc8bf84 Compare June 12, 2024 22:23
@gitstream-cm gitStream.cm
Copy link

gitstream-cm bot commented Jun 12, 2024

This PR is missing a Jira ticket reference in the title or description.
Please add a Jira ticket reference to the title or description of this PR.

@gitstream-cm gitStream.cm
Copy link

gitstream-cm bot commented Jun 12, 2024

🥷 Code experts: slavik-chapelskyi, irenhh

slavik-chapelskyi has most 👩‍💻 activity in the files.
slavik-chapelskyi, irenhh have most 🧠 knowledge in the files.

See details

package.json

Activity based on git-commit:

slavik-chapelskyi
JUN
MAY
APR 11 additions & 10 deletions
MAR
FEB
JAN

Knowledge based on git-blame:
slavik-chapelskyi: 57%
irenhh: 41%

To learn more about /:\ gitStream - Visit our Docs

@renovate renovate bot force-pushed the renovate/code-style-deps branch from bc8bf84 to 2ff2eb8 Compare July 13, 2024 23:17
@renovate renovate bot force-pushed the renovate/code-style-deps branch from 2ff2eb8 to 6bbc45e Compare August 3, 2024 22:20
@renovate renovate bot force-pushed the renovate/code-style-deps branch from 6bbc45e to 825d704 Compare August 14, 2024 21:55
@renovate renovate bot force-pushed the renovate/code-style-deps branch from 825d704 to 21f1fee Compare September 4, 2024 23:34
@renovate renovate bot force-pushed the renovate/code-style-deps branch from 21f1fee to c0d5906 Compare September 18, 2024 21:55
@renovate renovate bot force-pushed the renovate/code-style-deps branch from c0d5906 to 479fda0 Compare November 27, 2024 22:39
@renovate renovate bot force-pushed the renovate/code-style-deps branch 2 times, most recently from 171b5a4 to c3973a2 Compare December 11, 2024 22:00
@renovate renovate bot force-pushed the renovate/code-style-deps branch from c3973a2 to d24f059 Compare December 28, 2024 22:51
@renovate renovate bot force-pushed the renovate/code-style-deps branch 2 times, most recently from 699862a to dc6c11e Compare January 26, 2025 01:50
@renovate renovate bot force-pushed the renovate/code-style-deps branch from dc6c11e to 1caccc7 Compare January 29, 2025 23:20
@renovate renovate bot force-pushed the renovate/code-style-deps branch 2 times, most recently from f14b329 to 7157816 Compare February 16, 2025 00:22
@renovate renovate bot force-pushed the renovate/code-style-deps branch from 7157816 to 16b3a76 Compare February 23, 2025 00:21
@renovate renovate bot force-pushed the renovate/code-style-deps branch from 16b3a76 to aeee4f2 Compare March 6, 2025 02:32
@renovate renovate bot force-pushed the renovate/code-style-deps branch from aeee4f2 to f4fce47 Compare March 13, 2025 02:33
@renovate renovate bot force-pushed the renovate/code-style-deps branch from f4fce47 to 144acf8 Compare April 7, 2025 22:31
@renovate renovate bot force-pushed the renovate/code-style-deps branch 2 times, most recently from befb04e to b4d4677 Compare April 8, 2025 05:54
@renovate renovate bot force-pushed the renovate/code-style-deps branch from b4d4677 to ab512b0 Compare April 11, 2025 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
1 min review frontend missing-jira
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants