v4.2.10

f5d8d9b (Avoid unnecessary allocations for date binds, 2025-10-16)

v4.2.9

cff575f (Replace CollapseObjectArray with Object.fromEntries, 2025-10-16)

v4.2.8

Update dependency lint-staged to v16

Notable 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.
• #​1608 4e3ce22 Thanks @​srsatt! - Detect the git repo's top-level directory correctly when in a worktree.
• #​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.
• #​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.
• #​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.
• #​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.
• #​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.
• #​1558 c37dc38 Thanks @​iiroj! - The minimum required Node.js version is lowered to 20.17 following [email protected].
• #​1546 158d15c Thanks @​iiroj! - Processes are spawned using nano-spawn instead of execa. If you are using Node.js scripts as tasks, you might need to explicitly run them with node, especially when using Windows:
• #​1546 158d15c Thanks @​iiroj! - The --shell flag has been removed and lint-staged no longer supports evaluating commands directly via a shell. To migrate existing commands, you can create a shell script and invoke it instead. Lint-staged will pass matched staged files as a list of arguments, accessible via "$@​":

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

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](https://redirect...

v4.2.7

Update dependency peggy to v5

Notable changes

• Now supports testing with -t and -T with "amd", "umd", and "globals" format. Fork/exec no longer needed in basic generation path.
• Adjust repository's Git configuration around CR/LF normalization. #​639
• Now uses tsup for code generation instead of tsc and rollup. This may be user-visible, since tsup injects different polyfills than typescript was. #​644
• Fix unicode ranges whose upper bound is astral.
• Update dependencies.
• Tweak TypeScript output from --dts to make error type more clear. #​623
• Test on Node 24, but not Node 23.
• Write a message after failing a compile in watch mode.
• Fix TypeScript error in peg.d.ts, SyntaxError constructor should not have a return type.
• Add more Unicode to fizzbuzz example.
• Catch invalid unicode property escapes at compile time.
• Fix TypeScript error in peg.d.ts.
• Fix SyntaxError definition in peg.d.ts
• BREAKING: Generated code no longer supports ES5. You can still generate
• BREAKING: Node.js v20+ is now required for the CLI tools. No testing is
• BREAKING: The SyntaxError class exported from generated parsers is now a
• BREAKING: The grammar parser now uses your JavaScript environment's understanding
• Extend library mode to include a success flag and a function for throwing
• Slightly better verbose output from the CLI, showing where files are written.
• Merged class rules (rules which consist of a character class like
• Superfluous rules (rules which cannot be reached from an allowedStartRule)
• Character classes now process characters not in the Basic Multi-Lingual
• Unicode characters may now be specified with the \u{hex} syntax, allowing
• Errors pointing to non-BMP characters as the "found" text will now show the
• Character classes can now be annotated with the "u" flag, which will force
• Empty inverted character classes such as [^] or [^]u now match one
• String literals may now contain characters from outside the BMP.
• Character classes may now contain \p{} or \P{} escapes to match or
• A new "semantic" pass has been added to the compiler, which occurs after all
• Unreachable code in rules like 'b'* / 'c', ![], &[], !('f'*), and
• Globals, UMD, and CommonJS are now downloadable from the online version. The
• Switch to pnpm-action instead of corepack for GitHub Actions. Ensure that help text always wraps the same in tests, no matter the actual terminal width. #​588
• All libraries used in the web site brought up-to-date, versioned with all
• Code coverage increased for Peggy Grammar parser.
• Minor changes in code generation for parsers. More consistent indentation,
• Avoid performance cliff for deeply-nested grammars when checking for
• Small measures to try to get deno run -A npm:peggy to work. We will not
• Fix a bug with named NEVER_MATCH expressions.
• Warnings from grammar parsing are now presented more fully to the user in
• One of the intermediate files that is generated in tests was not getting
• Link to browserlist support matrix in documentation.
• When clicking on the link to the examples grammar, do not download the
• Set a minimum height for the editors in the online version.
• Update the docs for newly-created compiler passes. Make pluck and literal

peggyjs/peggy (peggy)

v5.0.6

Compare Source

Released: 2025-08-05

New features

• Now supports testing with -t and -T with "amd", "umd", and "globals" format. Fork/exec no longer needed in basic generation path.
  #​643

Bug fixes

• Adjust repository's Git configuration around CR/LF normalization. #​639
• Now uses tsup for code generation instead of tsc and rollup. This may be user-visible, since tsup injects different polyfills than typescript was. #​644

v5.0.5

Compare Source

Released: 2025-07-10

Bug fixes

• Fix unicode ranges whose upper bound is astral.
  #​636

v5.0.4

Compare Source

Released: 2025-06-20

Bug fixes

• Update dependencies.
  #​630

v5.0.3

Compare Source

Released: 2025-05-30

Bug fixes

• Tweak TypeScript output from --dts to make error type more clear. #​623
• Test on Node 24, but not Node 23.
  #​624
• Write a message after failing a compile in watch mode.
  #​624

Documentation

v5.0.2

Compare Source

Released: 2025-05-07

Bug fixes

• Fix TypeScript error in peg.d.ts, SyntaxError constructor should not have a return type.
  #​619
• Add more Unicode to fizzbuzz example.
  #​619
• Catch invalid unicode property escapes at compile time.
  #​619

v5.0.1

Compare Source

Released: 2025-05-07

Bug fixes

• Fix TypeScript error in peg.d.ts.
  #​615
• Fix SyntaxError definition in peg.d.ts
  #​616

v5.0.0

Compare Source

Released: 2025-05-03

Major Changes

• BREAKING: Generated code no longer supports ES5. You can still generate
  commonjs or es6 exports, but the code itself requires ES2020. If you need
  to support earlier runtimes, you should use a transpiler such as Babel.
  Generated code now uses const and let, but is still not strict about
  using const wherever possible, due to the complexities of code generation.
  Work-arounds and polyfills for class extension, padding, and Object.assign
  have been removed in favor of their ES2020 equivalents.
  #​593
• BREAKING: Node.js v20+ is now required for the CLI tools. No testing is
  performed on earlier versions of Node, and no issues will be fixed for
  earlier versions. #​593
• BREAKING: The SyntaxError class exported from generated parsers is now a
  proper subclass of the built-in ECMAscript SyntaxError class. The name of
  the type has changed to PeggySyntaxError, which may cause some slight need
  for rework in TypeScript-aware projects. This was the main driver behind
  moving away from ES5. #​593
• BREAKING: The grammar parser now uses your JavaScript environment's understanding
  of Unicode classes, rather than a partial copy of Unicode 8 as before. This
  should be more correct and evolve over time while staying backward-compatible
  to the extent that the Unicode Consortium keeps to its goals. Because this
  might slightly affect what rule names are valid, we are marking this as a
  breaking change just in case.
  #​602

New features

• Extend library mode to include a success flag and a function for throwing
  syntax errors when needed. Library mode is still intended as internal-only,
  and subject to backward-incompatible changes in future versions.
  #​501
• Slightly better verbose output from the CLI, showing where files are written.
  #​601
• Merged class rules (rules which consist of a character class like
  foo = [0-9] that are only called from a rule like bar = foo / [a-z], which
  merges the two classes together into a single rule like bar = [0-9a-z]),
  and which are not allowedStartRules, are no longer output into the generated
  parser, since there is no way for that code to be called. This has a chance
  of generating issues for people who are calling the internals of the
  generated parser using
  @​peggyjs/coverage, but that's a
  lightly-documented feature of that library.
  #​594
• Superfluous rules (rules which cannot be reached from an allowedStartRule)
  no longer generate code into the parser. An INFO-level debug statement is
  generated for each of these removals. Like merged class rules above, this
  should only be removing dead code.
  [#​594](https://redirect.github.com/peggyjs/peg...

v4.2.6

c1809b5 (Update @balena/lint to 9.x, 2025-04-09)

v4.2.5

3a782a7 (Improve typings, 2025-04-09)
0f71c04 (Tests: convert to typescript, 2025-04-09)

v4.2.4

2a6499f (Build: switch tsconfig to use module "Node16" with type "commonjs", 2025-04-09)

v4.2.3

4e1f975 (Avoid setting $count options for $orderby when not provided, 2025-03-11)

v4.2.2

Update dependency mocha to v11

Notable changes

• bump yargs to 17 (#​5165) (8f1c8d8)
• replace strip-ansi with util.stripVTControlCharacters (#​5267) (3c191c0), closes #​5265
• catch exceptions setting Error.stackTraceLimit (#​5254) (259f8f8)
• error handling for unexpected numeric arguments passed to cli (#​5263) (210d658)
• correct outdated status: accepting prs link (#​5268) (f729cd0)
• replace "New in" with "Since" in version annotations (#​5262) (6f10d12)
• bumped glob dependency from 8 to 10 (#​5250) (43c3157)
• fix examples for linkPartialObjects methods (#​5255) (34e0e52)
• adapt new engine range for Mocha 11 (#​5216)
• allow calling hook methods (#​5231) (e3da641)
• adapt new engine range for Mocha 11 (#​5216) (80da25a)
• downgrade example/tests chai to 4.5.0 (#​5245) (eac87e1)

mochajs/mocha (mocha)

v11.1.0

Compare Source

🌟 Features

• bump yargs to 17 (#​5165) (8f1c8d8)
• replace strip-ansi with util.stripVTControlCharacters (#​5267) (3c191c0), closes #​5265

v11.0.2

Compare Source

🩹 Fixes

• catch exceptions setting Error.stackTraceLimit (#​5254) (259f8f8)
• error handling for unexpected numeric arguments passed to cli (#​5263) (210d658)

📚 Documentation

• correct outdated status: accepting prs link (#​5268) (f729cd0)
• replace "New in" with "Since" in version annotations (#​5262) (6f10d12)

v11.0.1

Compare Source

🌟 Features

• bumped glob dependency from 8 to 10 (#​5250) (43c3157)

📚 Documentation

• fix examples for linkPartialObjects methods (#​5255) (34e0e52)

v11.0.0

Compare Source

⚠ BREAKING CHANGES

• adapt new engine range for Mocha 11 (#​5216)

🌟 Features

• allow calling hook methods (#​5231) (e3da641)

🩹 Fixes

• adapt new engine range for Mocha 11 (#​5216) (80da25a)

📚 Documentation

• downgrade example/tests chai to 4.5.0 (#​5245) (eac87e1)

List of commits

118d834 (Update dependency mocha to v11, 2025-03-18)

v4.2.1

dde8140 (Add the missing properties in the PropertyPath typings, 2025-03-14)
78efcd8 (Add the missing MethodCall type, 2025-03-18)