Back to Explore

SukkaW/nolyfill

GitHub
2 watchersOpen source

Last release:

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

  • Maintenance status: The most recent update in this source is 1.0.44 on 2025-03-04, and the upstream push was 2025-06-03, which is over 12 months ago from 2026-06-09, so the project appears quiet or in maintenance mode, not actively maintained.
  • Update cadence: Prior updates appear in bursts (for example, multiple 2024-07-22 and 2024-10-16/12-05), but there is a long gap after 2025-03/06. Overall, cadence looks infrequent and not steady.

AI summary generated

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

Recent updates

  • 1.0.44

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

    BreakingFeatures

  • 1.0.43

    Release 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

    Release 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).

    BreakingFeatures

  • 1.0.41

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

    BreakingFeatures

  • 1.0.40

    Release 1.0.40 introduces new generated polyfill packages (array-flatten, number-is-nan, safe-buffer, safer-buffer) and updates the CLI tooling and its lockfile handling. The provided release notes are empty, so this analysis focuses on the actual code and build-system changes present in the diff.

    Features

  • 1.0.39

    Release 1.0.39 contains no published release notes. The code diff shows several internal refactors and at least two likely breaking behavior or API surface changes, plus some packaging/build adjustments.

    Breaking

  • 1.0.38

    Release 1.0.38 primarily bumps package versions across the monorepo and makes internal changes to the @nolyfill/is-core-module build/runtime artifacts. Release notes were not provided, so the real behavior depends on the code diff, which shows mostly packaging and build-logic adjustments.

  • 1.0.37

    Release 1.0.37 appears to contain only package metadata updates. There are no functional code changes shown in the provided diff, and the publisher provided no release notes.

  • 1.0.36

    Release 1.0.36 contains a small but meaningful update to the @nolyfill/is-core-module package, including newly generated TypeScript typings and a change to how core module specifiers are recognized. The repository also updates the publish workflow to use Node 22 instead of Node 18. No release notes were provided, so all behavioral/build changes below are effectively undocumented.

    Features

  • 1.0.35

    Release 1.0.35 was published on 2024-07-22. No release notes or change details were provided by the publisher, so the impact of this upgrade is unclear from the release documentation alone.

  • v1.0.30

    Release 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

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

    The 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

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

    Features

  • v1.0.15

    Release 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

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