-
Notifications
You must be signed in to change notification settings - Fork 178
Module build failed: Error: File was not found in program #9
Comments
@erkieh There are no |
interesting, I'm getting same file not found errors even though they are in the path given by error message. P.S. it though emits a file, but still gives error? P.S.S. maybe this issue is Windows related?
Full error stack with awesome-typescript-loader:
|
The plot thickens, it does not compile with regular typescript-loader either at the moment, error is different: Stack trace with typescript-loader, not awesome one.
|
My configuration can't be simpler now: webpack.config.js:
index.ts:
Still same error. Maybe it is some Windows problem? Versions
|
@Ciantic thanks for the details. I will look at this issue tomorrow morning (GMT+3) from my PC with Windows. |
I'm now trying in fresh directory in shorter path, with same test files as above. Same error. Edit tried with TypeScript 1.5-alpha too, same error. Currently default with npm is 1.5-beta. |
@Ciantic yes, this is an error with backslashes on Windows. I'll fix this soon. |
seems like if I hack awesome-typescript-loader/dist/host.js with
Things start to work again. |
@Ciantic thanks, that fixed it for me too! |
fix(*): fix windows path logic, fixes #9
Looks like it is reproducible on Windows hosts again after update to 0.15... typescript: 1.8.0-dev.20151123 |
I just installed awesome-typescript-loader to see if this problem I had a month ago was fixed, and no.. I 'm having the same problem. awesome-typescript-loader is not recognising my internal files/modules starts with import something from './something' . I'm using windows. |
Any update on this? Is a fix on the way? We are having the same issue. A little different in that we are wild-carding the selection of the TS files but we get the same error. |
I have the same issue. For me, first of all, it depends on how many entry points I have (now I have 3). One of them is always compiled correctly and two of them are not. If I delete the succeeded entry point from the entries list the next will be compiled correctly and another one not. If I have only one entry point it is always compiled correctly. Another option is if I use compiled files from Visual Studio with |
I will look through the issue today. Does anyone has a little example I can play with? |
I have the same issue. With typescript 1.7.5 or 1.6.2 |
I am having the same issue after upgrading to 0.15.9. |
@frapontillo Same here. 0.15.8 also has the same issue. v0.15.7 works fine. |
@musakarakas +1 to this, 0.15.7 fixes the issue |
@musakarakas Looks like you're right 0.15.7 is the version to use. |
Could you please try v0.15.10? |
v0.15.10 works for me. No errors or warnings. |
I tried to add this typescript loader to the following sample project:
https://github.com/iam4x/isomorphic-flux-boilerplate
I get an error while running "npm run dev". I'm not sure how to proceed from here. The path in the error seems correct.
ERROR in ./app/components/orderEdit.ts
Module build failed: Error: File C:\i\app\components\orderEdit.ts was not found
in program
at State.emit (C:\i\node_modules\awesome-typescript-loader\dist\host.js:120:
23)
at C:\i\node_modules\awesome-typescript-loader\dist\index.js:92:42
at tryCatcher (C:\i\node_modules\awesome-typescript-loader\node_modules\blue
bird\js\main\util.js:24:31)
at Promise._settlePromiseFromHandler (C:\i\node_modules\awesome-typescript-l
oader\node_modules\bluebird\js\main\promise.js:454:31)
at Promise._settlePromiseAt (C:\i\node_modules\awesome-typescript-loader\nod
e_modules\bluebird\js\main\promise.js:530:18)
at Async._drainQueue (C:\i\node_modules\awesome-typescript-loader\node_modul
es\bluebird\js\main\async.js:182:12)
at Async._drainQueues (C:\i\node_modules\awesome-typescript-loader\node_modu
les\bluebird\js\main\async.js:187:10)
at Immediate.Async.drainQueues [as _onImmediate](C:inode_modulesawesome-
typescript-loadernode_modulesbluebirdjsmainasync.js:15:14)
at processImmediate as _immediateCallback
@ ./app/routes.jsx 31:13-46
The text was updated successfully, but these errors were encountered: