npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@alloc/resolve.exports

v1.2.1

Published

A tiny (854b), correct, general-purpose, and configurable "exports" resolver without file-system reliance

Downloads

15

Readme

@alloc/resolve.exports

An improved version of the acclaimed resolve.exports package.

  • written in TypeScript
  • prefer readability over code golfing
  • only 50% larger than the original package (+1.5kB, unminified)
  • tests use Vitest (100% test coverage)
  • code formatted with Prettier

 

API differences

This package exports a resolveExports function, whose type signature is incompatible with the original resolve.exports package. A few options have been removed or renamed to better fit the needs of Vite.

This package has no legacy function export.

This package only throws errors for invalid exports syntax. It returns an empty array if no modules are matched.

Fallback arrays

To support the "fallback array" feature (useful for glob patterns), the resolveExports function will always return an array of paths. If no matches are found, the array will be empty.

Renamed options

The require was renamed to isRequire to match the resolve options used by Vite internals. This allows Vite to avoid creating a new object for every call to resolveExports.

Removed options

The unsafe and browser options have been removed. There is no way to replicate the behavior of unsafe in this package. The browser option was removed because I want to leave room for future platform conditions (beyond just browser and node).

Bug fixes

The following issues from resolve.exports are fixed by this package:

  • https://github.com/lukeed/resolve.exports/issues/7
  • https://github.com/lukeed/resolve.exports/issues/9
  • https://github.com/lukeed/resolve.exports/issues/16
  • https://github.com/lukeed/resolve.exports/issues/17
  • https://github.com/lukeed/resolve.exports/issues/19

 

Type definitions

type ExportMapping = null | string | PackageExports | readonly ExportMapping[]
export type PackageExports = {
  [key: string]: ExportMapping
}
export type PackageJson = {
  name?: string
  exports?: ExportMapping
}
export interface ResolveExports {
  (
    pkg: PackageJson,
    entry: string,
    options?: ResolveExports.Options,
    inlineConditions?: string[]
  ): string[]
}
export namespace ResolveExports {
  export type Options = {
    /**
     * Custom conditions to match with.
     *
     * @example ['node']
     */
    conditions?: readonly string[]
    /**
     * When true, the `production` condition is used. Otherwise, the
     * `development` condition is used.
     */
    isProduction?: boolean
    /**
     * When true, the `require` condition is used. Otherwise, the
     * `import` condition is used.
     */
    isRequire?: boolean
  }
}