Skip to content
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

No Output using TypeScript 1.8.0 Beta #147

Closed
MikeRyanDev opened this issue Jan 28, 2016 · 8 comments
Closed

No Output using TypeScript 1.8.0 Beta #147

MikeRyanDev opened this issue Jan 28, 2016 · 8 comments

Comments

@MikeRyanDev
Copy link

Using the TypeScript 1.8.0 compiler I'm getting the following error:

ERROR in ./app/bootstrap.ts
Module build failed: Error: Typescript emitted no output for /demo-project/app/bootstrap.ts
    at Object.loader (/demo-project/node_modules/ts-loader/index.js:421:15)

I tried tracking it down and it seems like the name property for outputFiles has changed, but I couldn't find a corresponding breaking change for the TS compiler that would cause that to be the case.

@jbrantly
Copy link
Member

I'm unable to reproduce this, and according to the tests here the test suite runs fine on TS 1.8.

Assuming things work fine with TS 1.7.5 but fail with TS 1.8, my guess is that there was a change where your bootstrap.ts now causes TypeScript to not emit output for whatever reason. It would be interesting to run tsc against it and see what happens.

This is likely related to #91, meaning, if something in your file caused TypeScript to fail currently ts-loader isn't reporting what the issue is so it makes it hard to investigate/fix.

@MikeRyanDev
Copy link
Author

Ah, I was led me to believe it might be something to do with ts-loader as running tsc against the project works fine with TypeScript 1.8 .

Thanks for running the tests against 1.8! Verifies the problem is on my end somewhere.

@jbrantly
Copy link
Member

Definitely reopen if you feel like it might be a problem with ts-loader and we can try to figure it out.

@stepancar
Copy link

@jbrantly i have the same issue, after removing noEmit: true from tsconfig - it works fine

@kaw2k
Copy link

kaw2k commented Mar 2, 2016

Same here, removing noEmit: true it works

@adamlewy
Copy link

adamlewy commented Mar 3, 2016

removing noEmit: true is not a solution, we need it disabled in our flow but then we can't upgrade our Typescript version to 1.8

@stepancar
Copy link

@adamlewy see this comment works for me

@adamlewy
Copy link

adamlewy commented Mar 3, 2016

@stepancar overwriting "noEmit": false inside webpack config worked, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants