Back to Explore

juliangruber/balanced-match

GitHub
4 watchersOpen source

Last release:

balanced-match finds the first non-nested, matching pair of delimiter characters (or patterns), such as `{` and `}` or `<b>` and `</b>`, in a string. It returns the match positions and surrounding text (pre, body, post), or `undefined` if no match is found, and can also use regular expressions.

Project status

  • Actively maintained, with recent upstream activity (last push 2026-08-05) and npm updates in 2026 (v4.0.2 to v4.0.4 between 2026-02-09 and 2026-02-22).
  • Update cadence appears moderate and tooling-focused, with a small cluster of updates in February 2026, and later upstream commits in August 2026, but no evidence here of frequent feature releases.

AI summary generated

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • v4.0.4

    Release v4.0.4 updates project metadata and development tooling, including the Node.js engine range and CI test matrix. The diff shows no application/library source changes, but it does include a large lockfile update with multiple dependency version changes for the development/test toolchain.

    Security
  • v4.0.3

    Release v4.0.3 contains only package metadata and dependency-graph changes, with no application or source-code changes shown in the provided diff. The package version is bumped from 4.0.2 to 4.0.3, and the runtime dependency list is reduced by removing jackspeak from package.json while keeping it in the lockfile as a dev dependency.

  • v4.0.2

    Release v4.0.2 was published on 2026-02-09, but the publisher did not provide any release notes. Because no documented changes are available, developers should review the GitHub commit diff or changelog between v4.0.1 and v4.0.2 to identify any potential API, behavior, or dependency impacts before upgrading.

  • v3.0.1

    Release v3.0.1 updates the balanced-match package metadata and test/development dependency graph. The documented changes are switching package.json entry resolution from main to exports, and bumping minimist from 1.2.5 to 1.2.8, plus adding a CODE_OF_CONDUCT.md file.

    Breaking
  • v3.0.0

    v3.0.0 converts the package to ESM (package.json now has type: module, and index.js uses ESM exports). The release notes mostly claim a single major change, with additional tooling modernization and dependency bumps.

    Breaking
  • v2.0.0

    This release updates the project to version 2.0.0 with largely internal refactoring and repository/tooling changes. The runtime implementation in index.js is mostly the same logic, with modernized JavaScript syntax and formatting changes.

  • v1.0.2

    v1.0.2 is primarily a tooling and repo housekeeping release, reverting prior formatting and test tooling changes (standard/prettier-standard), undoing some matcha and np-related changes, and adjusting Travis configuration. The core library implementation in index.js appears to be the same algorithmically, with changes mainly related to formatting and build/dev setup.

  • v1.0.1

    v1.0.1 modernizes the project tooling (standard, prettier-standard, np) and CI config, and removes the Makefile in favor of npm scripts. It also includes a functional bug fix for cases where the opening and closing delimiters are the same, ensuring the returned `body` is no longer empty.

  • v1.0.0

    v1.0.0 is the first stable release of the library. The release notes provide no details on new features, bug fixes, breaking changes, security updates, or migration steps.