Same issue here - works with optimization disabled

Hi, we’d need some more details to determine from where the regression came;

1. Can you update Angular FW and CLI/Build-Angular individually and confirm which update causes the issue?

2. Can you kindly share the one of the classes that is causing the error?

Hi,

Updating individually gives the following results

• Angular FW rc.10 and CLI/Build-Angular rc.10 works
• Angular FW rc.11 and CLI/Build-Angular rc.10 works
• Angular FW rc.11 and CLI/Build-Angular rc.11 fails

or with --source-map

Possibly @Select from ngxs is causing the issue

Class is

import { Component, Input, OnInit } from '@angular/core';
import { Select, Store } from '@ngxs/store';
import { AppState } from '../app.state';
import { Observable, throwError } from 'rxjs';
import { MenuItem, ParentMenuItem, PlanMenuItem, StandardMenuItem } from '../menu/menu-item';
import { RemovePlanMenuItem } from '../menu/menu.actions';
import { catchError, debounceTime, first, take } from 'rxjs/operators';
import { ContextState } from '../shared/services/context.state';
import { User } from '../shared/user';
import { ContextService } from '../shared/services/context.service';
import { BackgroundType, SettingsService } from '../settings/settings.service';
import { environment } from '../../environments/environment';
import { HttpClient, HttpHeaders } from '@angular/common/http';
import { Meta } from '@angular/platform-browser';

@Component({
               selector: 'app-navigation',
               templateUrl: './navigation.component.html',
               styleUrls: ['./navigation.component.scss']
           })
export class NavigationComponent implements OnInit {
    @Select(AppState.standardMenuItems) standardMenuItems$: Observable<StandardMenuItem[]>;
    @Select(AppState.parentMenuItems) parentMenuItems$: Observable<ParentMenuItem[]>;
    @Select(AppState.planMenuItems) planMenuItems$: Observable<PlanMenuItem[]>;
    user: User;
    logoSource = 'assets/images/logo_dark.svg';
    @Input() title: string;
    logoutDisabled = false;
    showThemeMenu = false;
    private logoutUrl: string;

    constructor(private store: Store,
                public context: ContextService,
                private settingsService: SettingsService,
                private http: HttpClient,
                private meta: Meta) {
    }

    ngOnInit() {
        this.settingsService.backgroundType$
            .subscribe((bt: BackgroundType) => {
                this.logoSource = bt === 'dark' ? 'assets/images/logo_dark.svg' : 'assets/images/logo_light.svg';
            });

        this.store.select(ContextState.user)
            .pipe(first(user => !!user))
            .subscribe((user => {
                    this.user = user;
                    this.settingsService.setTheme(user, this.settingsService.getThemeFromLocalStorage(user));
            }));

        this.logoutUrl = this.meta.getTag('name=_casLogoutUrl').content;

        if (Storage) {
            this.showThemeMenu = true;
        }
    }

    close(item: MenuItem) {
        if (item instanceof PlanMenuItem) {
            return this.store.dispatch(new RemovePlanMenuItem(item.id));
        }
    }

    logOutClick() {
    }
}

Hi,

I'm seeing the same issue on my end with @angular-devkit/build-angular rc.11 and rc.12. I maintain the @lithiumjs/angular library, which is decorator-based like NGXS. I maintain an example app for the library that also makes use of NGXS. I'm seeing the same behavior when running ng serve --prod with @angular-devkit/build-angular rc.12:

The issue appears to happen with @Select from NGXS, and decorators like @StateEmitter and @EventSource from Lithium. As mentioned, setting optimization: false fixes the problem, but is not ideal of course. After enabling sourcemaps, I can see the error happens in my SessionUtils service on the following line:

Branch 4.0.0 of my example app project, which uses @angular-devkit/build-angular rc.10, works fine with ng serve --prod. I created another branch which simply updates the devkit version to rc.12, and that causes the above build issue with ng serve --prod.

Hopefully this helps. Thanks.

It appears that the common element is that all the projects have the emitDecoratorMetadata TypeScript option enabled. This option has not been required by Angular since version 8.0.4 and newly created projects no longer contain the option. Unless a third-party library or the application code specifically require the presence of the option, it can be safely removed. The need for this option is generally uncommon. Also of note is that the option generates code (more details) that has the potential to cause runtime errors with certain source code constructs.
However, for the cases where the option is required, a fix is currently being investigated.

@clydin Interesting, thanks for the info. Removing the use of ES7 reflection and emitDecoratorMetadata from the project does indeed resolve the issue with rc.12.

Wow thanks guys, removing emitDecoratorMetadata = true from my tsconfig.json fixed the issue for me too! I was looking everywhere to try and fix the broken build until finding this issue 🙌. I can only imagine plenty of other people will also face this cryptic issue, so the v9-blockers milestone is definitely warranted 💪

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