-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid System.import? #16
Comments
Just wanted to piggy back off this issue and provide some details around what sounds like a related experience running webpack within a gulp task. I've also posted at https://stackoverflow.com/questions/45491396/issue-with-ts-loaderawesome-typescript-loader-as-well-when-running-webpack-3-4 Given the following config(in file webpack.config.js) using either ts-loader or awesome-typescript-loader:
Running Given the following file, test.js:
Running But given the following gulp task:
Running
From what I can tell given the following block that System(in node_modules/loader-runner/lib/loadLoader.js) only defined when leveraging gulp and emitting an undefined result(i.e. module).
Can anyone help please? |
System.import was removed in v3 |
Hi, I've run into an interop problem between systemjs-builder and webpack running concurrently in the same process. In short, loader-runner picks up on the
System
global installed by systemjs due to this code path.I don't know if it's really loader-runner's fault, but I ended up solving my problem by forking it and cutting out that part. And now that webpack 2 went with
import(...)
instead ofSystem.import(...)
, is it still needed?The text was updated successfully, but these errors were encountered: