Skip to content

Cannot read property 'notifications' of undefined #214

Closed

Description

@danwkennedy

If the package.json file doesn't have an "angular-cli" field, calls to ng build will fail with the following error:

TypeError: [DiffingTSCompiler]: Cannot read property 'notifications' of undefined
    at DiffingTSCompiler.showNotification (..../node_modules/angular-cli/lib/broccoli/broccoli-typescript.js:196:38)

Activity

  1. filipesilva commented on Feb 18, 2016

    @filipesilva
    Contributor

    I believe this should be "fixed" in the latest master. By fixed though, I mean the notification functionality should be inadvertently gone and thus the notification check does not happen anymore.

    @hansl can you chime in? I'm following info from #134 (comment) together with #206

  2. danwkennedy commented on Feb 18, 2016

    @danwkennedy
    Author

    I found this on the latest master as of yesterday morning. I can try again on a later commit in a bit. The work around obviously is to add that option in package so it hasn't blocked me or anything

  3. filipesilva commented on Feb 18, 2016

    @filipesilva
    Contributor

    #206 happened 16h ago, I think that is when it changed.

  4. danwkennedy commented on Feb 18, 2016

    @danwkennedy
    Author

    Looks like it's fixed in 0.0.20 👍

  5. hansl commented on Feb 18, 2016

    @hansl
    Contributor

    @filipesilva: Yes, it was fixed. This is a non-issue for now :)

  6. filipesilva commented on Feb 18, 2016

    @filipesilva
    Contributor

    @hansl If it is indeed removed, then the rest of the changes introduced in the original PR should also be removed.

  7. hansl commented on Feb 18, 2016

    @hansl
    Contributor

    Agreed. If you don't have time for that I can do it.

  8. added a commit that references this issue on Jun 5, 2018
    7aec16f
  9. added a commit that references this issue on Jun 6, 2018
    cd0d619
  10. angular-automatic-lock-bot commented on Sep 5, 2019

    @angular-automatic-lock-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.

  11. locked and limited conversation to collaborators on Sep 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions