denoland / denoland/dnt

Customise shim per entrypoint

Open
#320 1 comment 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
Rust
Stars
1.3k
Forks
49
PR merge metrics
No merged PRs in 30d

Description

Hi! I have been using this package for a little while, and stumbled now upon a slight issue. When creating a multi-entrypoint package where each entrypoint supports a different subset of features, for example:

- one entrypoint for system, where fs and env is needed
- one entrypoint for browser, where document is needed
- one entrypoint for react components etc

It would be great if each entrypoint (the interface `EntryPoint`) would contain a `shims` property (interface `ShimOptions`) that would override the top-level `shims` property.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.