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

Hello there!

I've encountered a bug with the transpiling of the rest parameters.

Pratically the transpiler with something like this:

export function brokenArgsRest(fn, ...args) {
  return function () {
    fn(...args);
  };
}

Will treat the arguments object in the wrong way:

function brokenArgsRest(fn) {
  return function () {
    fn.apply(void 0, [].slice.call(

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

JSPM-mappings is not used by jest. Attempts to import front end dependencies in a test generates an error.

I am currently having a look at jest-jspm as a possible solution.