rollup

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 amd when creating build config

Suggested Solution

Consider support AMD module format, o

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

does this plugin support in-browser rollup setups?
i can't seem to get it to work (in a client-side setup without node).

in principle, however, rollup supports client-side bundling..

Running yarn build in the contracts package outputs a bunch of warnings.

1. We should fix the warnings

There are no serious risks from these warnings, but we should fix them because it's easy to do, and it's easy to become desensitized to them, which results in a gradually increasing number of warnings.

2. The build process should fail if there are warnings

Better to just pre