Skip to content

@ngtools/webpack not working with HMR after 8.0.0 and IVY enabled #15225

Closed

Description

@kukjevov

🐞 Bug report

Command (mark with an x)

- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

not using angular cli, but @ngtools/webpack

Is this a regression?

Yes in version 8.0.1 was working, 8.1.0 or higher is not working.

Description

When you change anythying in your template and HMR reloads script you will receive error that any directive or component that is used in that template is not known. When you stop HMR and rebuild application and run it again everything is working fine until you change something. I have another project and i cant move from 8.0.1 because this is only working version with Angular IVY, @ngtools/webpack and HMR.

🔬 Minimal Reproduction

download this https://github.com/kukjevov/ngtools-error

git clone https://github.com/kukjevov/ngtools-error
cd ngtools-error
npm install
npm start
open in browser http://localhost:8888 add

super
into eitherapp.component.htmlornavigation.component.html`
look for error in browser console

🔥 Exception or Error

if you change app.component.html you will get


Error: "Export of name 'outlet' not found!"

if you change navigation.component.html you will get


Error: "Template error: Can't bind to 'routerLinkActiveOptions' since it isn't a known property of 'div'."

🌍 Your Environment

  • angular and ngtools: 8.2.0
  • node: 10.16.0
  • npm: 6.9.0

Activity

  1. filipesilva commented on Aug 8, 2019

    @filipesilva
    Contributor

    Heya, I'm closing because angular/angular#31916 (comment) indicates this is an bug on the Framework repository and there is a fix on the way.

  2. angular-automatic-lock-bot commented on Sep 9, 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.

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