Using structural directive with ngFor, ngTemplateOutlet causes runtime error in production mode
See original GitHub issueI’m submitting a … (check one with “x”)
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
Current behavior
@Directive({
	selector: 'template[carouselItem]'
})
export class CarouselItem {
	id: string;
	constructor(public templateRef: TemplateRef<any>) {}
}
@Component({
	selector: 'carousel',
	template: `
	<div class="banner-group">
		<div class="banner" *ngFor="let item of item_list">
			<template [ngTemplateOutlet]="item.templateRef"></template>
		</div>
	</div>
	`
})
export class Carousel {
}
@Component({
  selector: 'my-app',
  template: `
    <carousel>
      <template ngFor let-t [ngForOf]="[0, 1]">
        <div *carouselItem>Test!</div>
      </template>
    </carousel>
  `
})
export class App {
}
This code worked fine until version 2.1.2. But after upgrading to 2.2.0 it is broken and showing this error.
core.umd.js:2840 TypeError: Cannot read property 'appendChild' of null
    at appendChild (platform-browser.umd.js:1200)
    at View_App1.visitRootNodesInternal (VM2335 component.ngfactory.js:123)
    at View_App1.AppView._renderAttach (core.umd.js:9256)
    at View_App1.AppView.attachAfter (core.umd.js:9234)
    at ViewContainer.attachView (core.umd.js:9561)
    at ViewContainerRef_.insert (core.umd.js:7137)
    at ViewContainerRef_.createEmbeddedView (core.umd.js:7117)
    at eval (common.umd.js:1338)
    at DefaultIterableDiffer.forEachOperation (core.umd.js:3343)
    at NgFor._applyChanges (common.umd.js:1336)
I don’t know much about Angular2’s internal code, but seems this error is caused by Direct renderer which is newly introduced by 2.2.0.
Minimal reproduction of the problem with instructions Working version (angular 2.1.2): http://plnkr.co/edit/qeIrSjXXCYJPKTwLxiIV Broken version (angular 2.2.0): http://plnkr.co/edit/wEhMdzVmANgB2a1TpOwU
Please tell us about your environment: macOS 10.12.1
- 
Angular version: 2.2.0
 - 
Browser: all
 - 
Language: TypeScript 2.0.3
 
Issue Analytics
- State:
 - Created 7 years ago
 - Reactions:6
 - Comments:10 (4 by maintainers)
 
Top Results From Across the Web
Wrap Angular ngFor directive with another structural directive
I'm trying to implement myDir in pair with myComponent to provide a templated wrapper over ngFor Angular core directive to be able to...
Read more >ngdart | Dart Package - Pub.dev
Renaming forked by AngularDart Community packages to be able publish and use them on pub.dev Resolving builds and tests. Fix complained test analyzis....
Read more >Angular 9's Best Hidden Feature: Strict Template Checking
Find and report more errors than ever with Angular 9's Ivy compiler, strict template checking.
Read more >ng-container - Angular
One common use case of <ng-container> is alongside the *ngIf structural directive. By using the special element we can produce very clean templates...
Read more >Angular Notes - rgbk21
You can install TypeScript using: npm install -g typescript ... application execution environments: Angular's rendering design makes it possible to support ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Hi, when will be next relase?
For me it is a serious mistake. My reproduction: http://plnkr.co/edit/tKeCv9gfp1wUw3VeL6Na?p=preview If you remove
*ngIf="!closed"inalert.tsit will be worked. Pls help 😦