Back to Explore

browserify/resolve

GitHub
1 updates · last 90 days1 watchersOpen source

Last release: 2 weeks ago

Implements the Node.js `require.resolve()` algorithm, letting you resolve a module specifier to the corresponding file path asynchronously or synchronously. It is useful when you need to determine where a module would resolve from a given `basedir`, including handling package `main` fields and `exports`-based resolution.

Project status

  • Actively maintained, with a recent upstream push on 2026-05-15 and continued work reflected in multiple v2.0.0-next updates after earlier activity.
  • Update cadence appears bursty, with v2.0.0-next.6 on 2026-02-16 and v2.0.0-next.7 on 2026-05-15, but the previous noted update was much older (2023-10-10).

AI summary generated Today

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

Recent updates

  • v2.0.0-next.7

    2 weeks ago

    Release v2.0.0-next.7 has no publisher release notes provided. The diff indicates new TypeScript declaration entry points and new runtime behavior around resolving package exports using a moduleSystem option (require vs import), plus several error-handling and environment-homedir edge-case fixes.

    Features

  • v2.0.0-next.6

    3 months ago

    Release v2.0.0-next.6 contains no publisher-provided release notes. The code diff shows a major internal change: new exports-resolution logic (including condition handling and exports-category selection) was added along with extensive new tests.

    Features

  • v2.0.0-next.5

    10/10/2023

    This release is version v2.0.0-next.5, but no release notes were provided by the publisher. As a result, there is insufficient information to identify new features, breaking changes, bug fixes, security updates, or other upgrade-impacting modifications from the release notes alone.