4.0.0 received no aot compilation error on { provide: 'windowObject', useValue: window },

[dereklin]

When I was using 2.4.9 and tried to build aot, there was a compilation error regarding this:

{ provide: 'windowObject', useValue: window },

I upgraded to 4.0.0, and didn't see the error. I thought Angular 4 is capable of understanding this usage now. I was wrong. In production at runtime, the window object is undefined.

In the end, I used the approach described here: https://juristr.com/blog/2016/09/ng2-get-window-ref/ and it works in 4.0.0

But if Angular 4 can't inject the window object with { provide: 'windowObject', useValue: window }, it should give an error during compilation like it did in 2.4.9.

[DzmitryShylovich]

Yeah, I can confirm that it doesn't throw during compilation but injects undefined.

[oleonardo]

I use this solution: Universal "Gotchas"

import { PLATFORM_ID, Component, Inject, OnInit } from '@angular/core';
import { isPlatformBrowser } from '@angular/common';
import { JQUERY_TOKEN } from './../../services/common/index';

@Component({
    selector: 'home',
    templateUrl: './home.component.html',
    styleUrls: ['./home.component.scss']
})
export class HomeComponent implements OnInit {
    constructor(
        @Inject(PLATFORM_ID) private platformId: Object,
        @Inject(JQUERY_TOKEN) private $: JQueryStatic
    ) {
    }

    ngOnInit() {
        //workaround to avoid break on server side prerendering
        if (!isPlatformBrowser(this.platformId)) return;

        let $window = this.$(window);
        console.log($window);
    }
}

It works well for me, I hope this helps you.

[JoostK]

I can no longer reproduce in Angular 9, neither using ViewEngine nor Ivy. Closing as resolved.

[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.}