Build for non-default System.constructor instance

[mikec...@gmail.com]

The bundle output generated by the builder defines define(), and references System.register() directly. When I import the bundle via a custom System.constructor instance, it is then referencing the wrong instance. How can I avoid this?

[Guy Bedford]

When importing a bundle with SystemJS, it will always use scoped evaluation that ensures the `System` reference is the current loader.

If that is not the case, then it is a bug, and a replication example would be useful.

On Fri, Jun 10, 2016 at 4:12 PM <mikec...@gmail.com> wrote:

The bundle output generated by the builder defines define(), and references System.register() directly. When I import the bundle via a custom System.constructor instance, it is then referencing the wrong instance. How can I avoid this?

--
You received this message because you are subscribed to the Google Groups "SystemJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to systemjs+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.