Just came across one of our client projects, which uses their own npm registry instead of the official one. By making it configurable via cli-flag like --registry https://my-registry.com we could support that use case.
I'm wondering if this is how we can make our npm plugin testable too! We could spin up a fake registry since we only ever download the tarball and use the --registry flag in
Tiny issue, great for a first-time contributor. Just need to delete these lines from the primary package.json:
examples no longer exists.
Add a description, image, and links to the rollup topic page so that developers can more easily learn about it.
To associate your repository with the rollup topic, visit your repo's landing page and select "manage topics."
Current Behavior
UMD build doesn't support code-splitting and dynamic imports (rollup/rollup#3490, rollup/rollup#3491) due to Rollup current limitations, and tsdx cli don't accept the format option
amdwhen creating build configSuggested Solution
Consider support AMD module format, o