nolyfill is a CLI tool for Node.js projects that identifies redundant polyfills in your existing dependencies and replaces them with lightweight alternatives. It is intended to speed up package installation (npm, yarn, pnpm), reduce disk usage by shrinking `node_modules`, and improve runtime performance by avoiding slower polyfill implementations when native support is available.
Project status
- The source appears to have ongoing activity, with a recent upstream push on 2025-06-03, but the tagged
updatesshown in the provided history are sparse (most recent documented tag is v1.0.30 on 2024-03-22). - Apparent update cadence is low, with at least a roughly 7 month gap between the 2023-08 beta tags and the 2024-03 v1.0.30 tag, and no additional documented tags after v1.0.30 in the provided data.
AI summary generated Today
Recent updates
1.0.44
3/4/2025Release 1.0.44 contains a large volume of changes across the project (about 300 files) with many additions in generated/type files and refactors in the ES-shim-like sources. The provided release notes are empty, so documented changes cannot be verified against the actual diff.
BreakingFeatures1.0.43
12/5/2024Release 1.0.43 contains a small workspace version bump and a change to the CLI lockfile parsing logic used to detect pnpm lockfile versions. There are no publisher-provided release notes, so all behavioral changes are effectively undocumented.
1.0.42
10/22/2024Release 1.0.42 has no provided release notes. The code diff shows a notable export-shape change for @nolyfill/array-flatten by adding a default export, which also alters CommonJS behavior, plus several dev tooling dependency bumps (eslint, stylistic plugins, typescript-eslint, picocolors).
BreakingFeatures1.0.41
10/18/2024Release 1.0.41 has no publisher-provided release notes. The code diff shows the CLI tool changed its version override strategy and update-check implementation, and the project added multiple new polyfill/shim packages.
BreakingFeaturesv1.0.30
3/22/2024Release v1.0.30 has no release notes content provided, so there is nothing documented to validate against the actual changes. The diff shows substantial repository and build-tooling changes, plus removal of multiple package entrypoint files under packages/* that could affect published package availability or behavior.
v1.0.16-beta.2
8/26/2023v1.0.16-beta.2 appears to be primarily a workspace release re-tagging from v1.0.16-beta.1. The provided code diff shows only package version string updates across the monorepo packages, with no functional code changes visible.
v1.0.16-beta.1
8/26/2023The publisher provided no release notes for v1.0.16-beta.1, so the specific code changes, feature additions, bug fixes, and potential breaking changes cannot be verified from the release description. Developers should avoid assuming compatibility changes are documented, and instead review the corresponding commits or changelog in the repository before upgrading.
v1.0.16-beta.0
8/26/2023Release v1.0.16-beta.0 contains no published release notes. The code diff shows the addition of new polyfill packages (deep-equal, es-aggregate-error, promise.any) and updates to the nolyfill CLI, especially how it scans dependency lockfiles and detects the package manager.
Featuresv1.0.15
8/24/2023Release v1.0.15 was published on 2023-08-24, but no release notes were provided by the publisher. As a result, there is no documented information about new features, breaking changes, bug fixes, security fixes, or dependency updates in this release.
v0.0.1
8/9/2023This appears to be the initial release (v0.0.1) and no publisher release notes were provided. Because there are no documented changes, you should review the tagged code diffs and API surface area before upgrading, especially for any new or experimental functionality.