ng build fails

ng build: BuildingENOENT: no such file or directory, open \src\client\tsconfig.json’

Windows 7 node: v4.3.0 npm: 2.14.12 angular-cli: 0.0.30

What i did: npm update the cli was specified in the package.json (“angular-cli”: “0.0.*”) now its specific to 0.0.30, i tried 0.0.29 which give me:

 csucsi@csucsi-PC  /cygdrive/c/Users/csucsi/Documents/work/slaychat/src  ng build
BuildingCannot read property 'map' of undefined
TypeError: Cannot read property 'map' of undefined
    at Angular2App.toTree (C:\Users\csucsi\Documents\work\slaychat\node_modules\angular-cli\lib\broccoli\angular2-app.js:64:34)
    at module.exports (C:\Users\csucsi\Documents\work\slaychat\angular-cli-build.js:9:14)
    at Class.module.exports.Task.extend.setupBroccoliBuilder (C:\Users\csucsi\Documents\work\slaychat\node_modules\angular-cli\node_modules\angular-cli\lib\models\builder.js:55:19)
    at Class.module.exports.Task.extend.init (C:\Users\csucsi\Documents\work\slaychat\node_modules\angular-cli\node_modules\angular-cli\lib\models\builder.js:89:10)
    at new Class (C:\Users\csucsi\Documents\work\slaychat\node_modules\angular-cli\node_modules\angular-cli\node_modules\core-object\core-object.js:18:12)
    at Class.module.exports.Task.extend.run (C:\Users\csucsi\Documents\work\slaychat\node_modules\angular-cli\node_modules\angular-cli\lib\tasks\build.js:15:19)
    at C:\Users\csucsi\Documents\work\slaychat\node_modules\angular-cli\node_modules\angular-cli\lib\commands\build.js:28:24
    at lib$rsvp$$internal$$tryCatch (C:\Users\csucsi\Documents\work\slaychat\node_modules\angular-cli\node_modules\angular-cli\node_modules\rsvp\dist\rsvp.js:1036:16)
    at lib$rsvp$$internal$$invokeCallback (C:\Users\csucsi\Documents\work\slaychat\node_modules\angular-cli\node_modules\angular-cli\node_modules\rsvp\dist\rsvp.js:1048:17)
    at lib$rsvp$$internal$$publish (C:\Users\csucsi\Documents\work\slaychat\node_modules\angular-cli\node_modules\angular-cli\node_modules\rsvp\dist\rsvp.js:1019:11)

Full log with version 0.0.30:

 csucsi@csucsi-PC  /cygdrive/c/Users/csucsi/Documents/work/slaychat/src  ng build
BuildingENOENT: no such file or directory, open 'C:\Users\csucsi\Documents\work\slaychat\src\client\tsconfig.json'
Error: ENOENT: no such file or directory, open 'C:\Users\csucsi\Documents\work\slaychat\src\client\tsconfig.json'
    at Error (native)
    at Object.fs.openSync (fs.js:549:18)
    at Object.fs.readFileSync (fs.js:397:15)
    at Angular2App.toTree.Angular2App._getTsTree (C:\Users\csucsi\Documents\work\slaychat\node_modules\angular-cli\lib\broccoli\angular2-app.js:229:32)
    at Angular2App.toTree (C:\Users\csucsi\Documents\work\slaychat\node_modules\angular-cli\lib\broccoli\angular2-app.js:37:21)
    at module.exports (C:\Users\csucsi\Documents\work\slaychat\angular-cli-build.js:9:14)
    at Class.module.exports.Task.extend.setupBroccoliBuilder (C:\Users\csucsi\Documents\work\slaychat\node_modules\angular-cli\node_modules\angular-cli\lib\models\builder.js:55:19)
    at Class.module.exports.Task.extend.init (C:\Users\csucsi\Documents\work\slaychat\node_modules\angular-cli\node_modules\angular-cli\lib\models\builder.js:89:10)
    at new Class (C:\Users\csucsi\Documents\work\slaychat\node_modules\angular-cli\node_modules\angular-cli\node_modules\core-object\core-object.js:18:12)
    at Class.module.exports.Task.extend.run (C:\Users\csucsi\Documents\work\slaychat\node_modules\angular-cli\node_modules\angular-cli\lib\tasks\build.js:15:19)
 ✘  csucsi@csucsi-PC  /cygdrive/c/Users/csucsi/Documents/work/slaychat/src 

Toughts:

It’s just can find the tsconfig in a non existing folder, somehow its trying to look it up deeper than it should.

• src
  • tsconfig.js

and not

• src
  • client
    • tsconfig.js

[0x-r4bbit]

In angular-cli 0.0.30 there’s a client folder between src/ and app. So now, when you generate a project, it’s src/client/app not src/app.

See https://github.com/angular/angular-cli/commit/a5ddd75f3f11a2a7b267e6c242f983c3594a8765 for more information

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}