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

Currently, mangle.json writes always remove a trailing newline from the file. We could detect the existence of the trailing newline when reading, then preserve whatever was used when writing.

See https://github.com/preactjs/preact/blob/e22cc99ca398bb0a417ccc151a520c41215afe55/.editorconfig#L17-L22

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..

See @mslipper's comment here:

Originally posted by @mslipper in ethereum-optimism/optimism#1559 (comment)

We ought to:

• Push builder at a tagged version (i.e., in the same way that the canary and other versioning pipelines work)
• Pull ethereumoptimism/builder from that version by using ARG in each Dockerfile