[deps]: Update npm minor #12

renovate · 2024-07-22T01:53:03Z

This PR contains the following updates:

Package	Change	Age	Confidence
husky	`9.0.11` -> `9.1.7`
lint-staged	`16.0.0` -> `16.2.5`
prettier (source)	`3.3.2` -> `3.6.2`

Release Notes

typicode/husky (husky)

`v9.1.7`

Compare Source

What's Changed

fix: add husky label to deprecated warning by @smackfu in #1538

New Contributors

@smackfu made their first contribution in #1538

Full Changelog: typicode/husky@v9.1.6...v9.1.7

`v9.1.6`

Compare Source

What's Changed

Fix issue where example pre-commit file is generated incorrectly by @dexmlee in #1519

New Contributors

@OlegKipchatov made their first contribution in #1495
@Byron2016 made their first contribution in #1499
@dexmlee made their first contribution in #1519

Full Changelog: typicode/husky@v9.1.5...v9.1.6

`v9.1.5`

Compare Source

What's Changed

fixes #1494, support pre-merge-commit hook by @RainMeoCat in #1497

New Contributors

@RainMeoCat made their first contribution in #1497

Full Changelog: typicode/husky@v9.1.4...v9.1.5

`v9.1.4`

Compare Source

Improve deprecation notice

`v9.1.3`

Compare Source

fix: better handle space in PATH

`v9.1.2`

Compare Source

Show a message instead of automatically removing deprecated code.

This only concerns projects that still have the following code in their hooks:

- #!/usr/bin/env sh # <- This is deprecated, remove it
- . "$(dirname -- "$0")/_/husky.sh"  # <- This is deprecated, remove it

### Rest of your hook code

Hooks with these lines will fail in v10.0.0

`v9.1.1`

Compare Source

Super saiyan ~~god~~ dog! It's over 9.0.0!

What's new

You can now run package commands directly, no need for npx or equivalents.
It makes writing hooks more intuitive and is also slightly faster 🐺⚡️

### .husky/pre-commit
- npx jest
+ jest # ~0.2s faster

A new recipe has been added to the docs. Lint staged files without external dependencies (inspired by Prettier docs). Feel free to modify it.

### .husky/pre-commit
prettier $(git diff --cached --name-only --diff-filter=ACMR | sed 's| |\\ |g') --write --ignore-unknown
git update-index --again

For more advanced use cases, see lint-staged.

Fixes

bunx husky init command
Workaround for some hooks implementation on Windows

Deprecations

#!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" are deprecated. husky command will automatically remove them, no action required.
If you're having code in ~/.huskyrc please move it to .config/husky/init.sh

Support for these will be removed in v10.

Friendly reminder

If Git hooks don't fit your workflow, you can disable Husky globally. Just add export HUSKY=0 to .config/husky/init.sh.

I've seen some confusion about this on X, so just a heads-up!

Sponsoring

Husky is downloaded over 45M times per month and used by ~1.5M projects. If your company wants to sponsor, you can do so here: GitHub Sponsors.

Have a nice summer ☀️ I'm open to new opportunities/consulting so feel free to drop me a message 😉

`v9.1.0`

Compare Source

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

`v16.2.5`

Compare Source

Patch Changes

#1687 9e02d9d Thanks @iiroj! - Fix unhandled promise rejection when spawning tasks (instead of the tasks themselves failing). Previously when a task failed to spawn, lint-staged also failed and the backup stash might not have been automatically restored.

`v16.2.4`

Compare Source

Patch Changes

#1682 0176038 Thanks @iiroj! - Update dependencies, including [email protected] with bug fixes.
#1671 581a54e Thanks @iiroj! - Speed up execution by only importing the yaml depedency if using YAML configuration files.

`v16.2.3`

Compare Source

Patch Changes

#1669 27cd541 Thanks @iiroj! - When using --fail-on-changes, automatically hidden (partially) unstaged changes are no longer counted to make lint-staged fail.

`v16.2.2`

Compare Source

Patch Changes

#1667 699f95d Thanks @iiroj! - The backup stash will not be dropped when using --fail-on-changes and there are errors. When reverting to original state is disabled (via --no-revert or --fail-on-changes), hidden (partially) unstaged changes are still restored automatically so that it's easier to resolve the situation manually.

Additionally, the example for using the backup stash manually now uses the correct backup hash, if available:

% npx lint-staged --fail-on-changes
✔ Backed up original state in git stash (c18d55a3)
✔ Running tasks for staged files...
✖ Tasks modified files and --fail-on-changes was used!
↓ Cleaning up temporary files...

✖ lint-staged failed because `--fail-on-changes` was used.

Any lost modifications can be restored from a git stash:

  > git stash list --format="%h %s"
  c18d55a3 On main: lint-staged automatic backup
  > git apply --index c18d55a3

`v16.2.1`

Compare Source

Patch Changes

#1664 8277b3b Thanks @iiroj! - The built-in TypeScript types have been updated to more closely match the implementation. Notably, the list of staged files supplied to task functions is readonly string[] and can't be mutated. Thanks @outslept!
```
export default {
---  "*": (files: string[]) => void console.log('staged files', files)
+++  "*": (files: readonly string[]) => void console.log('staged files', files)
}
```
#1654 70b9af3 Thanks @iiroj! - This version has been published from GitHub Actions using Trusted Publishing for npm packages.
#1659 4996817 Thanks @iiroj! - Fix searching configuration files when the working directory is a subdirectory of a git repository, and there are package.json files in the working directory. This situation might happen when running lint-staged for a single package in a monorepo.
#1654 7021f0a Thanks @iiroj! - Return the caret semver range (^) to direct dependencies so that future patch and minor versions are allowed. This enables projects to better maintain and deduplicate their own transitive dependencies while not requiring direct updates to lint-staged. This was changed in 16.2.0 after the vulnerability issues with chalk and debug, which were also removed in the same version.

Given the recent vulnerabilities in the npm ecosystem, it's best to be very careful when updating dependencies.

`v16.2.0`

Compare Source

Minor Changes

#1615 99eb742 Thanks @iiroj! - Added a new option --fail-on-changes to make lint-staged exit with code 1 when tasks modify any files, making the precommit hook fail. This is similar to the git diff --exit-code option. Using this flag also implies the --no-revert flag which means any changes made by tasks will be left in the working tree after failing, so that they can be manually staged and the commit tried again.
#1611 cd05fd3 Thanks @rlorenzo! - Added a new option --continue-on-error so that lint-staged will run all tasks to completion even if some of them fail. By default, lint-staded will exit early on the first failure.
#1637 82fcc07 Thanks @iiroj! - Internal lint-staged errors are now thrown and visible in the console output. Previously they were caught with the process exit code set to 1, but not logged. This happens when, for example, there's a syntax error in the lint-staged configuration file.
#1647 a5ecc06 Thanks @iiroj! - Remove debug as a dependency due to recent malware issue; read more at debug-js/debug#1005. Because of this, the DEBUG environment variable is no longer supported — use the --debug to enable debugging
#1636 8db2717 Thanks @iiroj! - Added a new option --hide-unstaged so that lint-staged will hide all unstaged changes to tracked files before running tasks. The changes will be applied back after running the tasks. Note that the combination of flags --hide-unstaged --no-hide-partially-staged isn't meaningful and behaves the same as just --hide-unstaged.

Thanks to @ItsNickBarry for the idea and initial implementation in #1552.
#1648 7900b3b Thanks @iiroj! - Remove lilconfig to reduce reliance on third-party dependencies. It was used to find possible config files outside of those tracked in Git, including from the parent directories. This behavior has been moved directly into lint-staged and should work about the same.

Patch Changes

#1633 7f9e485 Thanks @dependabot! - Bumps listr2 from 9.0.3 to 9.0.4.
#1626 99d5a9b Thanks @iiroj! - Due to recent phishing attacks, for example [email protected] was released with malware. To avoid lint-staged's users being at risk the direct dependencies are pinned to exact versions, instead of allowing future patch versions with the caret (^) range.
#1588 035bbf2 Thanks @outslept! - Increase performance by listing staged files and searching for configuration concurrently.
#1645 deba3ad Thanks @iiroj! - Remove chalk as a dependency due to recent malware issue; read more at chalk/chalk#656.

If you are having trouble with ANSI color codes when using lint-staged, you can try setting either FORCE_COLOR=true or NO_COLOR=true env variables.

`v16.1.6`

Compare Source

Patch Changes

#1610 e93578e Thanks @iiroj! - Try to improve terminating of subprocess of tasks by using SIGKILL, and only calling pidtree when the the main task process has a known pid.

`v16.1.5`

Compare Source

Patch Changes

#1608 4e3ce22 Thanks @srsatt! - Detect the git repo's top-level directory correctly when in a worktree.

`v16.1.4`

Compare Source

Patch Changes

#1604 90b37b0 Thanks @iiroj! - Add another types field to package.json to make even more sure NPM detects that lint-staged includes built-in TypeScript type definitions.

`v16.1.3`

Compare Source

Patch Changes

#1602 7ea700b Thanks @dword-design! - Add the types field to package.json to make sure NPM detects lint-staged includes built-in TypeScript type definitions.

`v16.1.2`

Compare Source

Patch Changes

#1570 a7c0c88 Thanks @ItsNickBarry! - When using --diff-filter with the D option to include deleted staged files, lint-staged no longer tries to stage the deleted files, unless they're no longer deleted. Previously this caused an error from git add like fatal: pathspec 'deleted-file' did not match any files.
38f942e Thanks @iiroj! - Removed an extraneous log entry that printed shouldHidePArtiallyStagedFiles to console output.

`v16.1.1`

Compare Source

Patch Changes

#1565 3686977 Thanks @iiroj! - Lint-staged now explicitly warns about potential data loss when using --no-stash.
#1571 02299a9 Thanks @iiroj! - Function tasks (introduced in v16.0.0) only receive the staged files matching the configured glob, instead of all staged files.
#1563 bc61c74 Thanks @iiroj! - This version fixes incorrect behavior where unstaged changes were committed when using the --no-stash option. This happened because --no-stash implied --no-hide-partially-staged, meaning unstaged changes to files which also had other staged changes were added to the commit by lint-staged; this is no longer the case.

The previous (incorrect) behavior can still be achieved by using both options --no-stash --no-hide-partially-staged at the same time.

`v16.1.0`

Compare Source

Minor Changes

#1536 e729daa Thanks @iiroj! - A new flag --no-revert has been introduced for when task modifications should be applied to the index before aborting the commit in case of errors. By default, lint-staged will clear all task modifications and revert to the original state.
#1550 b27fa3f Thanks @iiroj! - Lint-staged now ignores symlinks and leaves them out from the list of staged files.

Patch Changes

#1558 c37dc38 Thanks @iiroj! - The minimum required Node.js version is lowered to 20.17 following [email protected].

prettier/prettier (prettier)

`v3.6.2`

Compare Source

diff

Markdown: Add missing blank line around code block (#17675 by @fisker)

<!-- Input -->
1. Some text, and code block below, with newline after code block

   ```yaml
   ---
   foo: bar
   ```

   1. Another
   2. List

<!-- Prettier 3.6.1 -->
1. Some text, and code block below, with newline after code block

   ```yaml
   ---
   foo: bar
   ```
   1. Another
   2. List

<!-- Prettier 3.6.2 -->
1. Some text, and code block below, with newline after code block

   ```yaml
   ---
   foo: bar
   ```

   1. Another
   2. List

`v3.6.1`

Compare Source

diff

TypeScript: Allow const without initializer (#17650, #17654 by @fisker)

// Input
export const version: string;

// Prettier 3.6.0 (--parser=babel-ts)
SyntaxError: Unexpected token (1:21)
> 1 | export const version: string;
    |                     ^

// Prettier 3.6.0 (--parser=oxc-ts)
SyntaxError: Missing initializer in const declaration (1:14)
> 1 | export const version: string;
    |              ^^^^^^^^^^^^^^^

// Prettier 3.6.1
export const version: string;

Miscellaneous: Avoid closing files multiple times (#17665 by @43081j)

When reading a file to infer the interpreter from a shebang, we use the
n-readlines library to read the first line in order to get the shebang.

This library closes files when it reaches EOF, and we later try close the same
files again. We now close files only if n-readlines did not already close
them.

`v3.6.0`

Compare Source

diff

🔗 Release Notes

`v3.5.3`

Compare Source

diff

Flow: Fix missing parentheses in `ConditionalTypeAnnotation` (#17196 by @fisker)

// Input
type T<U> = 'a' | ('b' extends U ? 'c' : empty);
type T<U> = 'a' & ('b' extends U ? 'c' : empty);

// Prettier 3.5.2
type T<U> = "a" | "b" extends U ? "c" : empty;
type T<U> = "a" & "b" extends U ? "c" : empty;

// Prettier 3.5.3
type T<U> = "a" | ("b" extends U ? "c" : empty);
type T<U> = "a" & ("b" extends U ? "c" : empty);

`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.

Configuration

📅 Schedule: Branch creation - "every 2nd week starting on the 2 week of the year before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

github-actions · 2024-09-24T14:35:12Z

Checkmarx One – Scan Summary & Details – 410b0a73-649b-4c21-9f5b-bcf2b24e97f2

No New Or Fixed Issues Found

renovate bot requested a review from a team July 22, 2024 01:53

renovate bot added the version:patch label Jul 22, 2024

renovate bot force-pushed the renovate/npm-minor branch 3 times, most recently from a3b2653 to be1d1cb Compare July 29, 2024 15:35

renovate bot force-pushed the renovate/npm-minor branch from be1d1cb to 256ac6b Compare August 3, 2024 11:02

renovate bot force-pushed the renovate/npm-minor branch from 256ac6b to 733c8f2 Compare August 13, 2024 07:02

renovate bot force-pushed the renovate/npm-minor branch from 733c8f2 to 85736dd Compare August 20, 2024 14:43

renovate bot force-pushed the renovate/npm-minor branch from 85736dd to 197e679 Compare September 1, 2024 16:17

renovate bot force-pushed the renovate/npm-minor branch 3 times, most recently from 1223399 to ff44f11 Compare September 12, 2024 01:51

renovate bot force-pushed the renovate/npm-minor branch 2 times, most recently from db11399 to bb96342 Compare September 24, 2024 14:32

renovate bot force-pushed the renovate/npm-minor branch from bb96342 to 9d63a43 Compare October 3, 2024 13:56

renovate bot force-pushed the renovate/npm-minor branch 3 times, most recently from 917fc78 to c8306cc Compare October 22, 2024 16:10

renovate bot requested a review from a team as a code owner October 22, 2024 16:10

renovate bot force-pushed the renovate/npm-minor branch 5 times, most recently from 55b7ef3 to 2e94d33 Compare November 6, 2024 15:06

renovate bot force-pushed the renovate/npm-minor branch 5 times, most recently from 55b34d9 to 73c21a8 Compare November 11, 2024 14:50

renovate bot force-pushed the renovate/npm-minor branch from 893fb78 to ecc0158 Compare January 26, 2025 14:38

renovate bot force-pushed the renovate/npm-minor branch 2 times, most recently from e307a55 to 9a41997 Compare February 20, 2025 13:28

renovate bot force-pushed the renovate/npm-minor branch from 9a41997 to 5292479 Compare March 1, 2025 04:51

renovate bot force-pushed the renovate/npm-minor branch from 5292479 to 2c95695 Compare March 10, 2025 04:57

renovate bot force-pushed the renovate/npm-minor branch from 2c95695 to 050e888 Compare March 19, 2025 17:53

renovate bot force-pushed the renovate/npm-minor branch from 050e888 to 611c056 Compare April 18, 2025 19:17

renovate bot force-pushed the renovate/npm-minor branch from 611c056 to c85a597 Compare May 13, 2025 12:50

renovate bot force-pushed the renovate/npm-minor branch 2 times, most recently from 9cafee5 to abc9ffd Compare June 3, 2025 18:27

renovate bot force-pushed the renovate/npm-minor branch 2 times, most recently from 085c9fa to 9f967d5 Compare June 22, 2025 10:52

renovate bot force-pushed the renovate/npm-minor branch 3 times, most recently from f866b0c to 4c3769d Compare July 4, 2025 04:23

renovate bot force-pushed the renovate/npm-minor branch 3 times, most recently from f5fd5c9 to cb99277 Compare August 15, 2025 19:25

renovate bot force-pushed the renovate/npm-minor branch from cb99277 to eab8fae Compare August 19, 2025 11:36

renovate bot force-pushed the renovate/npm-minor branch from eab8fae to bb5bc34 Compare August 31, 2025 12:03

renovate bot force-pushed the renovate/npm-minor branch from bb5bc34 to 98a7754 Compare September 8, 2025 16:14

renovate bot force-pushed the renovate/npm-minor branch 2 times, most recently from 63e2660 to c8befb3 Compare September 29, 2025 06:55

renovate bot force-pushed the renovate/npm-minor branch 3 times, most recently from 6b34a14 to b0a7026 Compare October 5, 2025 14:10

renovate bot force-pushed the renovate/npm-minor branch 2 times, most recently from 7f35f40 to 7f83d9f Compare October 21, 2025 14:21

[deps]: Update npm minor

31fd134

renovate bot force-pushed the renovate/npm-minor branch from 7f83d9f to 31fd134 Compare October 27, 2025 20:59

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

[deps]: Update npm minor #12

[deps]: Update npm minor #12

renovate bot commented Jul 22, 2024 •

edited

Loading

Uh oh!

github-actions bot commented Sep 24, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

[deps]: Update npm minor #12

Are you sure you want to change the base?

[deps]: Update npm minor #12

Conversation

renovate bot commented Jul 22, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

What's Changed

New Contributors

What's Changed

New Contributors

What's Changed

New Contributors

What's new

Fixes

Deprecations

Friendly reminder

Sponsoring

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Markdown: Add missing blank line around code block (#​17675 by @​fisker)

TypeScript: Allow const without initializer (#​17650, #​17654 by @​fisker)

Miscellaneous: Avoid closing files multiple times (#​17665 by @​43081j)

Flow: Fix missing parentheses in ConditionalTypeAnnotation (#​17196 by @​fisker)

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

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

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

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

Fix comments print on class methods with decorators (#​16891 by @​fisker)

Fix non-idempotent formatting (#​16899 by @​seiyab)

Remove unnecessary parentheses around assignment in v-on (#​16887 by @​fisker)

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

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

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

Configuration

Uh oh!

github-actions bot commented Sep 24, 2024

No New Or Fixed Issues Found

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Jul 22, 2024 •

edited

Loading

Markdown: Add missing blank line around code block (#17675 by @fisker)

TypeScript: Allow const without initializer (#17650, #17654 by @fisker)

Miscellaneous: Avoid closing files multiple times (#17665 by @43081j)

Flow: Fix missing parentheses in `ConditionalTypeAnnotation` (#17196 by @fisker)

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

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

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

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

Fix comments print on class methods with decorators (#16891 by @fisker)

Fix non-idempotent formatting (#16899 by @seiyab)

Remove unnecessary parentheses around assignment in `v-on` (#16887 by @fisker)

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

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

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