Skip to content

Typings mismatch error after update and running ng new #1311

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

Closed
keithmichelson opened this issue Jul 9, 2016 · 3 comments
Closed

Typings mismatch error after update and running ng new #1311

keithmichelson opened this issue Jul 9, 2016 · 3 comments

Comments

@keithmichelson
Copy link

keithmichelson commented Jul 9, 2016

Please provide us with the following information:

  1. OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
    OSX El Capitan
  1. Versions. Please run ng --version. If there's nothing outputted, please
    run in a Terminal:
    node --version
    And paste the result here.
    angular-cli: 1.0.0-beta.9
    node: 4.0.0
    os: darwin x64
  2. Repro steps. Was this an app that wasn't created using the CLI? What change did you
    do on your code? etc.
    Just did an update using the 3 steps under Global Packets, then created a new probject using ng new
  3. The log given by the failure. Normally this include a stack trace and some
    more information.
    [email protected] postinstall: typings install
    Exit status 1

Then when running ng serve
The Broccoli Plugin: [Funnel] failed with:
Error: Attempting to watch missing directory: typings
at EventEmitter.Watcher_addWatchDir as addWatchDir

  1. Mention any other details that might be useful.

    Thanks! We'll be in touch soon.

@keithmichelson keithmichelson changed the title Error: Attempting to watch missing directory: typings Typings mismatch error after update Jul 9, 2016
@keithmichelson keithmichelson changed the title Typings mismatch error after update Typings mismatch error after update and running ng new Jul 9, 2016
@keithmichelson
Copy link
Author

Didn't see #1092 but it is still happening.
Did this as well and it worked:
npm run postinstall

@filipesilva
Copy link
Contributor

Closed as issue was made obsolete by #1455. On the next release we are not using typings anymore.

In your case the problem happened because we updated typings versions.

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants