Back to Explore

un-ts/pkgr

GitHub
1 watchersOpen source

Last release:

@unts/pkgr is a set of simple utilities for package bundlers like rollup and webpack. It is useful for bundling-related tasks, with features aligned to UMD and global handling.

Project status

  • Active maintenance: The repo shows ongoing work, with an upstream push on 2026-08-12 and multiple package updates in late May 2026 across @pkgr/core, @pkgr/utils, and @pkgr/rollup.
  • Update cadence (as evidenced here): Updates clustered tightly in 2026-05-28 to 2026-05-31, then no package updates are listed after that, while the upstream activity suggests development may continue without tagged package changes.

AI summary generated

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

Recent updates

  • @pkgr/rollup@7.1.0

    This release (@pkgr/rollup 7.1.0) is presented as a minor update to support newer Vite and Rollup plugin ecosystem versions. The code diff also includes a few internal behavior and toolchain changes, plus substantial dependency bumps across the rollup package and related workspace packages.

    Features
  • @pkgr/utils@4.1.0

    This release of @pkgr/utils@4.1.0 adds a new optional parameter, preferDefault, to the tryRequirePkg helper. When enabled, tryRequirePkg will prefer a module's default export (when available) over its CommonJS export shape.

    Features
  • @pkgr/core@0.2.10

    Release @pkgr/core@0.2.10 is a patch update that is documented as a fix for cases where `require.extensions` may be `undefined`. Code changes also include an internal refactor of `findUp` search path traversal logic, which is not mentioned in the release notes.

  • @pkgr/core@0.3.6

    This release is tagged as @pkgr/core@0.3.6 and the release notes only mention a small patch around deprecated require.extensions potentially being undefined. However, the actual diff from @pkgr/core@0.2.10 to @pkgr/core@0.3.6 includes broader internal refactors in core path and package discovery helpers, plus removals/behavior changes that are not reflected in the notes.

  • @pkgr/utils@4.0.1

    This release is documented as a patch change intended to rebuild @pkgr/utils with a newer @pkgr/core version correctly. The provided diff mostly shows publishing workflow adjustments and metadata updates (version and changelog), with no direct source or API code changes visible.

  • @pkgr/rollup@7.0.1

    This is a patch release of @pkgr/rollup 7.0.1. The release notes describe only an internal cleanup of constants, with no documented API, behavior, or migration changes.

  • @pkgr/core@0.3.5

    Release @pkgr/core@0.3.5 is described as a patch that 'cleans up constants'. The code changes are more than cosmetic: core constants were refactored to stop exporting CWD, and multiple call sites now default to process.cwd() directly. The repository also includes broader dependency and peerDependency bumps that are not mentioned in the release notes.

  • @pkgr/core@0.2.9

    This release is labeled as a republish of the 0.2.x line for @pkgr/core@0.2.9, with minimal release notes. The actual code diff shows a behavioral change in the `findUp` helper (less likely to throw, different search traversal behavior), along with some release-process configuration updates.

  • @pkgr/core@0.3.4

    The release notes for @pkgr/core@0.3.4 only state “republish the latest version” and do not describe any functional changes. However, the actual diff includes a significant refactor of @pkgr/core filesystem helpers, especially around the findUp and tryFile APIs, plus broader repo build/config updates.

  • @pkgr/core@0.3.3

    Release @pkgr/core@0.3.3 is a patch update. It primarily fixes how the findUp helper interprets and merges its options when called with different argument shapes.