-
Notifications
You must be signed in to change notification settings - Fork 178
Build process hangs after completion #302
Comments
I also have the exact same issue where the build hangs after successful completion. I reverted back to v3.0.0-beta.10 and that works. It appears to be broken from v3.0.0-beta.11 onwards. I'm using webpack v1.14.0, and typescript 2.1.4 |
I'm also experiencing the same issue with the following setup: "devDependencies": {
"typescript": "^2.1.4",
"webpack": "^1.14.0",
"awesome-typescript-loader": "^3.0.0-beta.12",
"source-map-loader": "^0.1.5"
} |
It hangs with |
@s-panferov no, it hangs on a standard build. It completed the build and everything looks fine but the process never terminates. |
@charsleysa which OS do you have? |
@s-panferov I have Windows 10 (latest stable channel release) but this issue also occurs on Linux Docker images. |
I have this problem too with osx sierra/node-yarn-7.2.0(docker image), [email protected] awesome-typescript-loader@^3.0.0-beta.12 and webpack@^2.1.0-beta.27. I have to different bundles in the same project. One works. The other don't. Haven't figured out why yet.. |
@s-panferov I'm experiencing this as well, the process just hangs after. webpack --progress --bail -p
webpack -p
webpack --bail
webpack All produce this result. With [email protected], [email protected] and [email protected] on MacOS 10.12.1 |
It looks like that forked process doesn't allow a parent to die. |
Fixed in [email protected], but unfortunately, the fix requires |
Can confirm that it works for me now! |
I have found that the build hangs after successful completion with v3.0.0-beta.12.
Works fine if I revert to v3.0.0-beta.9.
Haven't tested with other versions.
The text was updated successfully, but these errors were encountered: