Webpack failure targeting typescript

@swarner wrote:

After converting the stock application (from the cutePuppyPics example) to typescript, webpack responds with:

./www/app/app.js
Module build failed: Error: File C:/Users/user/Documents/test/cutePuppyPics/www/app/app.js wa
s not found in program
at State.emit (C:\Users\user\Documents\test\cutePuppyPics\node_modules\awesome-typescript
-loader\dist\host.js:102:23)
at transform (C:\Users\user\Documents\test\cutePuppyPics\node_modules\awesome-typescript-
loader\dist\index.js:350:36)
at C:\Users\user\Documents\test\cutePuppyPics\node_modules\awesome-typescript-loader\dist
\index.js:385:24
at tryCatcher (C:\Users\user\Documents\test\cutePuppyPics\node_modules\awesome-typescript
-loader\node_modules\bluebird\js\main\util.js:26:23)
at Promise.settlePromiseFromHandler (C:\Users\user\Documents\test\cutePuppyPics\nodemod
ules\awesome-typescript-loader\node_modules\bluebird\js\main\promise.js:507:31)
at Promise.settlePromiseAt (C:\Users\user\Documents\test\cutePuppyPics\nodemodules\awes
ome-typescript-loader\node_modules\bluebird\js\main\promise.js:581:18)
at Async.drainQueue (C:\Users\user\Documents\test\cutePuppyPics\nodemodules\awesome-typ
escript-loader\node_modules\bluebird\js\main\async.js:128:12)
at Async.drainQueues (C:\Users\user\Documents\test\cutePuppyPics\nodemodules\awesome-ty
pescript-loader\node_modules\bluebird\js\main\async.js:133:10)
at Immediate.Async.drainQueues [as _onImmediate] (C:\Users\user\Documents\test\cutePuppyP
ics\node_modules\awesome-typescript-loader\node_modules\bluebird\js\main\async.js:15:14)
at processImmediate as _immediateCallback
@ multi main (CLI v2.0.0-alpha.23)

Your system information:

Cordova CLI: 5.4.0
Ionic Version: 2.0.0-alpha.31
Ionic CLI Version: 2.0.0-alpha.23
Ionic App Lib Version: 2.0.0-alpha.22
OS: Windows 7 SP1
Node Version: v0.12.6

Compiling the typescript files externally and running produces the same error, despite the presence of a app.ts file. If loaders related to the awesome-typescript-loader are commented out, the build webpack completes successfully. Is there any known fix for this, or should I modify the webpack to utilize a different typescript loader?

Additionally, I noticed that ionic-framework@2.0.0-alpha.31 does not maintain the same directory format for typescript as it does for es5/es6 -- there should be an intermediary ionic folder so that calls to 'ionic/ionic' can be maintained when node_modules/ionic-framework/dist/typescript is added as a resource root (which prevents internal ionic modules which reference ionic/ionic from breaking, as well as external application modules). Is there any plan to correct this in a future release?

Posts: 1

Participants: 1

Read full topic