Skip to content

mat-table + ivy + elements + serve + scss = error #32426

Closed

Description

@flash-me

I'll sum it up:

  • I have an angular element (AppComponent).
  • I have 'enableIvy' = true & aot = true
  • I use SCSS in seperate files
  • I do have a valid setup. So far this only happens with mat-table
  • I don't use third party builders. Standard ng serve
  • Only reload with dev-server breaks, build etc. are fine
  • Any change in SCSS files that are included in compilation will cause error
  • (!)(!)No caching problem. This also happens with build --watch, the created bundles are corrupt(!)(!) You have to restart the build / serve task completely.

So far the workarounds are (one Of):

  • Inline SCSS changes do not cause break
  • Disable aot for ng serve
  • Disable ivy for ng serve

Reproduction

Github Repo: https://github.com/kqadem/ivy-test

Steps to reproduce:

  1. npm start
  2. change sth in src/app/app.component.scss, linebreak is enough
  3. refresh browser

Expected Behavior

I was expection the usual behaviour --> Run without any issues

Actual Behavior

Error at bootstrap / startup / Initializing with following error:
image

Environment

  • Angular: 8.2.0 (error still happens with 9-next)
  • CDK/Material: 8.1.4
  • Browser(s): Chrome 76
  • Operating System (e.g. Windows, macOS, Ubuntu): So far tested on Windows 7 and Ubuntu 19.04

Activity

  1. added this to the needsTriage milestone on Sep 1, 2019
  2. JoostK commented on Nov 1, 2019

    @JoostK
    Member

    I'm hoping that #33522 will resolve this issue, I'll test your repro with my PR to confirm over the weekend.

  3. JoostK commented on Nov 2, 2019

    @JoostK
    Member

    While it was indeed failing as you describe with 8.2.13. I have tested this with 9.0.0-rc.0 and are no longer able to reproduce.

    Please upgrade using

    ng update @angular/cli @angular/core --next --force
    
  4. angular-automatic-lock-bot commented on Dec 3, 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.

  5. locked and limited conversation to collaborators on Dec 3, 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

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions