Skip to content

Use package exports for shim #3468

@jthoward64

Description

@jthoward64

Is there an existing issue that is already proposing this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe it

Currently to use this package in a common library, we have to use resolver overrides which can be brittle and tedious to maintain.

Describe the solution you'd like

Use conditional exports to export the main entry (probably under "node" or "require") point as well as the shim under "browser" or "default" (and maybe "react-native" too?).

Teachability, documentation, adoption, migration strategy

No response

What is the motivation / use case for changing the behavior?

Make less work and remove some surprises from end users.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions