a new project with 0.37 doesn't run with ng serve #616

metric152 · 2016-05-03T19:57:39Z

OSX 10.11.3

angular-cli: 0.0.37
node: 4.4.3
os: darwin x64

create a new project with ng new p
cd into the project and run ng serve
project doesn't start and dumps a log to console

Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
Cannot read property 'sourceDir' of undefined
TypeError: Cannot read property 'sourceDir' of undefined
at new Angular2App (/Users/eleitch/tmp/p/node_modules/angular-cli/lib/broccoli/angular2-app.js:30:40)
at module.exports (/Users/eleitch/tmp/p/angular-cli-build.js:6:10)
at Class.module.exports.Task.extend.setupBroccoliBuilder (/Users/eleitch/tmp/p/node_modules/angular-cli/node_modules/angular-cli/lib/models/builder.js:55:19)
at Class.module.exports.Task.extend.init (/Users/eleitch/tmp/p/node_modules/angular-cli/node_modules/angular-cli/lib/models/builder.js:89:10)
at new Class (/Users/eleitch/tmp/p/node_modules/angular-cli/node_modules/angular-cli/node_modules/core-object/core-object.js:18:12)
at Class.module.exports.Task.extend.run (/Users/eleitch/tmp/p/node_modules/angular-cli/node_modules/angular-cli/lib/tasks/serve.js:15:19)
at /Users/eleitch/tmp/p/node_modules/angular-cli/node_modules/angular-cli/lib/commands/serve.js:64:24
at lib$rsvp$$internal$$tryCatch (/Users/eleitch/tmp/p/node_modules/angular-cli/node_modules/angular-cli/node_modules/rsvp/dist/rsvp.js:1036:16)
at lib$rsvp$$internal$$invokeCallback (/Users/eleitch/tmp/p/node_modules/angular-cli/node_modules/angular-cli/node_modules/rsvp/dist/rsvp.js:1048:17)
at /Users/eleitch/tmp/p/node_modules/angular-cli/node_modules/angular-cli/node_modules/rsvp/dist/rsvp.js:331:11
at lib$rsvp$asap$$flush (/Users/eleitch/tmp/p/node_modules/angular-cli/node_modules/angular-cli/node_modules/rsvp/dist/rsvp.js:1198:9)
at nextTickCallbackWith0Args (node.js:420:9)
at process._tickCallback (node.js:349:13)

Select one of the following:

I am filing a bug.

In this case you need the following information:

OS. Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Versions. Please run ng --version. If there's nothing outputted, please
run in a Terminal:

    node --version
    npm --version
    npm info angular-cli

And paste the result here.
3. Repro steps. Tell us exactly what you did and how you came to the failure.
If you can give us steps from the moment you created an empty application,
even better! Please try to be as descriptive as you can; this will avoid
unnecessary back and forth. Was this an app that wasn't created using the
CLI? What change did you do on your code? etc.
4. The log given by the failure. Normally this include a stack trace and some
more information.
5. Mention any other details that might be useful.

Thanks! We'll be in touch soon.

I am filing a feature request.

Unfortunately, for now, although we accept proposals, it will be probably be
deferred. It's not that we don't want to hear you, it's that we're focusing
on the beta release and as such we want to keep things a bit tidier than it
will be once this is out in the open.

We're not closed to good ideas, we simply have a limited amount of bandwidth.
There's only 24 hours per day.

I want customer support / I don't know how to do X.

This is unfortunately not the right place. Please join the discussion on
gitter, Stack Overflow or twitter and don't be afraid to post your
questions there. A FAQ will be created with those and it will help answer
questions other people might have as well.

I want to help!

Please read our contributing guidelines;
https://github.com/angular/angular-cli/blob/master/CONTRIBUTING.md

If you really want to be part of the crew and start cracking,
try to contact us on gitter. We're never really far and we might have
something just for you!

The text was updated successfully, but these errors were encountered:

metric152 · 2016-05-03T21:05:10Z

I solved the problem. The generated angular-cli.json file is missing a few new properties.
The defaults property was missing. I also had to add the sourceDir child property. After adding these it worked again.

{
  "routes": [],
  "defaults": {
      "sourceDir": "src/client"
  }
}

metric152 · 2016-05-03T21:18:55Z

The page will start up but not output anything to dist/vendor. Still working on this.

metric152 · 2016-05-03T21:44:12Z

Finally got it working again. All the node_module includes must be specified in angular-cli-build.js

vendorNpmFiles: ["es6-shim/es6-shim.js",
                    "systemjs/dist/system-polyfills.js",
                    "angular2/bundles/angular2-polyfills.js",
                    "systemjs/dist/system.src.js",
                    "rxjs/bundles/Rx.js",
                    "angular2/bundles/angular2.dev.js",
                    "angular2/bundles/http.dev.js",
                    "angular2/bundles/router.dev.js"]
  });

hansl · 2016-05-04T15:52:55Z

Yes. We now never copy your vendor files automatically. You have to specify them.

Also we don't use bundles locally anymore, but that depends on your systemJS configuration and might not be a problem.

Here's our current vendor list:

    vendorNpmFiles: [
      'systemjs/dist/system-polyfills.js',
      'systemjs/dist/system.src.js',
      'zone.js/dist/*.js',
      'es6-shim/es6-shim.js',
      'reflect-metadata/*.js',
      'rxjs/**/*.js',
      '@angular/**/*.js'
    ]

sharpmachine · 2016-05-10T18:27:51Z

the @angular/**/*.js doesn't work.

sharpmachine · 2016-05-10T18:31:04Z

I'm also wondering why you won't include those for us? After running ng new we then have to go in make sure our angular-build-cli.js includes all those things manually? That seems like a step backwards.

metric152 · 2016-05-10T18:37:47Z

I had to nuke my old generated code and place it in a newly configured project. It moved from 0.0.3x to 1.0.0-beta within a few days. Lots of changes happened all at once.

sharpmachine · 2016-05-10T18:48:22Z

@metric152 I ran npm update angular-cli and it updated it from 0.0.37 to 0.0.39. I can't get it to update to beta :/

hansl · 2016-05-10T18:57:14Z

@sharpmachine You shouldn't build new projects with anything older than the beta.

As for upgrading to the latest beta, try npm install -g angular-cli@beta or just npm install -g angular-cli@latest.

Federico-Comesana · 2016-06-13T20:17:57Z

@hansl I tried to run "npm install -g angular-cli@latest" but then I run "ng -v" and still getting an older version 0.0.39.
How can I force to download latest beta version?

metric152 · 2016-06-13T21:24:45Z

Try upgrade instead of install

On Monday, June 13, 2016, Federico-Comesana notifications@github.com
wrote:

@hansl https://github.com/hansl I tried to run "npm install -g
angular-cli@latest" but then I run "ng -v" and still getting an older
version 0.0.39.
How can I force to download latest beta version?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#616 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AANCOrRYOyqPJq-Vmy5VmWHLUT68dGdkks5qLbsAgaJpZM4IWkMQ
.

filipesilva · 2016-06-17T01:10:32Z

@Federico-Comesana we recently added https://github.com/angular/angular-cli#updating-angular-cli, it should help you upgrade.

Federico-Comesana · 2016-06-17T21:03:45Z

@filipesilva I've followed your link and still have an old angular-cli version (now is 0.0.33).

Do am I missing something?
I had run:

npm uninstall -g angular-cli
npm cache clean
npm install -g angular-cli@latest

I'm running "ng -v" in my home folder.

My environment:

Ubuntu 14.04.4 LTS
angular-cli: 0.0.33
node: 5.11.1
npm: 3.8.6

filipesilva · 2016-06-18T01:18:48Z

@Federico-Comesana that's really weird. Try forcing the version manually npm install -g angular-cli@1.0.0-beta.6.

sambanthar · 2016-09-21T10:13:42Z

just need to update everytime i need to uninstall and install again i need to migrate my project to latest one its not good

dchinn · 2016-12-07T17:59:31Z

update instructions don't work for me either. currently latest is 22, and , even after following the 'update' instructions, i'm stuck at beta 15

angular-automatic-lock-bot · 2019-09-06T10:42:12Z

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.}

metric152 mentioned this issue May 4, 2016

Cannot read property 'sourceDir' of undefined #619

Closed

hansl closed this as completed May 4, 2016

Aidurber mentioned this issue May 17, 2016

Build error The Broccoli Plugin: [BroccoliTypeScriptCompiler] failed with: #782

Closed

angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

a new project with 0.37 doesn't run with ng serve #616

a new project with 0.37 doesn't run with ng serve #616

metric152 commented May 3, 2016

We're not closed to good ideas, we simply have a limited amount of bandwidth.
There's only 24 hours per day.

This is unfortunately not the right place. Please join the discussion on
gitter, Stack Overflow or twitter and don't be afraid to post your
questions there. A FAQ will be created with those and it will help answer
questions other people might have as well.

metric152 commented May 3, 2016

metric152 commented May 3, 2016

metric152 commented May 3, 2016

hansl commented May 4, 2016

sharpmachine commented May 10, 2016 •

edited

Loading

sharpmachine commented May 10, 2016

metric152 commented May 10, 2016

sharpmachine commented May 10, 2016

hansl commented May 10, 2016

Federico-Comesana commented Jun 13, 2016

metric152 commented Jun 13, 2016

filipesilva commented Jun 17, 2016

Federico-Comesana commented Jun 17, 2016

filipesilva commented Jun 18, 2016

sambanthar commented Sep 21, 2016

dchinn commented Dec 7, 2016

angular-automatic-lock-bot bot commented Sep 6, 2019

a new project with 0.37 doesn't run with ng serve #616

a new project with 0.37 doesn't run with ng serve #616

Comments

metric152 commented May 3, 2016

We're not closed to good ideas, we simply have a limited amount of bandwidth. There's only 24 hours per day.

This is unfortunately not the right place. Please join the discussion on gitter, Stack Overflow or twitter and don't be afraid to post your questions there. A FAQ will be created with those and it will help answer questions other people might have as well.

metric152 commented May 3, 2016

metric152 commented May 3, 2016

metric152 commented May 3, 2016

hansl commented May 4, 2016

sharpmachine commented May 10, 2016 • edited Loading

sharpmachine commented May 10, 2016

metric152 commented May 10, 2016

sharpmachine commented May 10, 2016

hansl commented May 10, 2016

Federico-Comesana commented Jun 13, 2016

metric152 commented Jun 13, 2016

filipesilva commented Jun 17, 2016

Federico-Comesana commented Jun 17, 2016

filipesilva commented Jun 18, 2016

sambanthar commented Sep 21, 2016

dchinn commented Dec 7, 2016

angular-automatic-lock-bot bot commented Sep 6, 2019

We're not closed to good ideas, we simply have a limited amount of bandwidth.
There's only 24 hours per day.

This is unfortunately not the right place. Please join the discussion on
gitter, Stack Overflow or twitter and don't be afraid to post your
questions there. A FAQ will be created with those and it will help answer
questions other people might have as well.

sharpmachine commented May 10, 2016 •

edited

Loading