quick-format-unescaped formats values into a printf-like string (for example, using placeholders like %s, %j, and %d). It is useful when you need to embed formatted output into another string and escape the whole string, and it supports a custom stringify option. By default it uses JSON.stringify instead of util.inspect, so functions will not be serialized.
Project status
- Maintenance status: This GitHub source appears quiet/dormant, with the most recent upstream push on 2022-03-19 and the latest listed update v4.0.4 on 2021-09-21 (several years ago relative to 2026-08-12).
- Update cadence: Updates are sporadic and multi-year, with major version changes in 2018 to 2021, and no evident recent momentum after 2022.
AI summary generated
Recent updates
v4.0.4
v4.0.4 changes the behavior of the core `format(f, args, opts)` implementation and updates the test suite to match. Notably, it alters how non-string first arguments and extra trailing arguments are handled, and it introduces additional format specifiers.
v4.0.0
Release v4.0.0 contains a small code change but with behavior impact in the core formatter. The main change is that `format(f, args, opts)` now immediately returns `f` when `f` is not a string, removing the prior special handling for `f === null`.
v3.0.3
Release v3.0.3 contains no provided release notes. The code changes are small but materially affect how the formatter handles non-object values, specifically Symbols, and the test suite was updated to assert this behavior.
v3.0.2
Release v3.0.2 (published 2019-02-05) has no release notes from the publisher. The code diff and accompanying test and README changes indicate an API and parsing behavior update to the core `format` function, plus new CI coverage via Travis.
v3.0.0
v3.0.0 makes a significant change to the public API and formatting logic in index.js, including a new function signature and different handling of format arguments. The repository release notes are absent (none provided), so these changes are not documented in the release description.
Featuresv2.0.1
Release v2.0.1 changes only the package metadata in package.json. No release notes were provided by the publisher, so the change rationale is unclear.
v2.0.0
This release is labeled v2.0.0, but no release notes were provided by the publisher, so the specific code or behavior changes are not documented here. Developers should review the repository diff (especially public APIs, configuration, and changelog/commit history) before upgrading, since the version bump may imply breaking changes.