-
Notifications
You must be signed in to change notification settings - Fork 164
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
Webpack issues: Module build failed: Error: Typescript emitted no output for ... #134
Comments
Hmm, first time I see this. Thanks for reporting it. I'll look in to it. 👍 |
@flauc Same issue here :s |
Same issue using Angular 2.4.0 with webpack 1.13.2 and TS 2.1.4 |
I'd like to use angular2-notifications, but can't because of this bug.. do you have any idea when it can be fixed? |
similar here with angular 4.0.0-beta.8 and typescript 2.2.0 ERROR in angular2-notifications/src/push-notifications.service.ts |
same there with angular 4 rc2 and webpack/typescript edit: one workaround is to ensure js are loaded before ts so
and not
|
@rmannibucau This fixed my issue for a completely different package. Why does that work? |
cause webpack will match the file resolution in this "order". The issue is the ts not being supported anymore (nothing to convert to js basically). Loading the js before you will get a version not going through the exact same validations and or based on a different model (depends a bit other parts of the build). Concretely in that case the "empty" ts file is not seen and the build sees an actual js file which doesnt break the validations rules. |
@rmannibucau Thanks for the explanation, it makes a lot more sense now. |
Hi everyone, think this has been resolved with the latest push, let me know if you are still getting it though. |
This is still happening to me and was resolved by changing the order of extensions as suggested above:
thanks! here's my setup FYI:
|
I recently upgraded angular to
2.4.1
, and angular2-notifications to0.4.49
, and now I'm getting the following errors when I run webpack:The text was updated successfully, but these errors were encountered: