Error: Runtime compiler is not loaded #5460

mikeumus · 2017-03-16T23:22:41Z

Bug Report or Feature Request (mark with an `x`)

bug report

Versions.

1.0.0-rc.2

Repro steps.

ng build -prod -e prod

The log given by the failure.

vendor.380a744….bundle.js:218 Error: Runtime compiler is not loaded
    at new Error (native)
    at Error.d (http://localhost:9000/portal/assets/dist/polyfills.a61f849adcea6ec74b69.bundle.js:36:1731)
    at r (http://localhost:9000/portal/assets/dist/vendor.380a74466a8bf08fbdda.bundle.js:1410:3338)
    at t.compileModuleAndAllComponentsAsync (http://localhost:9000/portal/assets/dist/vendor.380a74466a8bf08fbdda.bundle.js:1417:702)
    at e.ngOnChanges (http://localhost:9000/portal/assets/dist/main.f4b767a4fe115c7bb97e.bundle.js:1:1171229)
    at e.ngDoCheck (http://localhost:9000/portal/assets/dist/main.f4b767a4fe115c7bb97e.bundle.js:1:914180)
    at t.GGjx.t.detectChangesInternal (http://localhost:9000/portal/assets/dist/main.f4b767a4fe115c7bb97e.bundle.js:1:332790)
    at t.R2h3.t.detectChanges (http://localhost:9000/portal/assets/dist/vendor.380a74466a8bf08fbdda.bundle.js:653:5749)
    at t.Sqya.t.detectChangesInNestedViews (http://localhost:9000/portal/assets/dist/vendor.380a74466a8bf08fbdda.bundle.js:667:780)
    at t.GGjx.t.detectChangesInternal (http://localhost:9000/portal/assets/dist/main.f4b767a4fe115c7bb97e.bundle.js:1:329907)
    at t.R2h3.t.detectChanges (http://localhost:9000/portal/assets/dist/vendor.380a74466a8bf08fbdda.bundle.js:653:5749)
    at t.R2h3.t.internalDetectChanges (http://localhost:9000/portal/assets/dist/vendor.380a74466a8bf08fbdda.bundle.js:653:5542)
    at t.YSmj.t.detectChangesInternal (http://localhost:9000/portal/assets/dist/main.f4b767a4fe115c7bb97e.bundle.js:1:662563)
    at t.R2h3.t.detectChanges (http://localhost:9000/portal/assets/dist/vendor.380a74466a8bf08fbdda.bundle.js:653:5749)
    at t.Sqya.t.detectChangesInNestedViews (http://localhost:9000/portal/assets/dist/vendor.380a74466a8bf08fbdda.bundle.js:667:780)

Desired functionality.

App to run with no errors.

Mention any other details that might be useful.

I've taken a lot of time to make sure my app is matching packages and conventions of a fresh cli-rc2 app (ng new) with no luck yet.

The text was updated successfully, but these errors were encountered:

clydin · 2017-03-16T23:35:59Z

A production build uses AOT by default which does not use the runtime compiler.
Also, the '-e prod' is unnecessary when '--prod' is used.

mikeumus · 2017-03-17T05:07:12Z

@clydin yeah I just thought ng build -prod --prod made less sense. So it there a way to get content hashed file names without the AoT?

I'm trying ng build --prod -aot false but am getting this error in the browser:

polyfills.a61f849….bundle.js:36 Unhandled Promise rejection: Cannot read property 'features' of undefined ; Zone: angular ;

sorakthun · 2017-03-18T15:57:53Z

@mikeumus has this issue been resolved yet? I'm facing similiar error with ng build --prod

EXCEPTION: Uncaught (in promise): Error: Runtime compiler is not loaded Error: Runtime compiler is not loaded at y (http://localhost:52094/polyfills.bc16906638c50c8e5423.bundle.js:36:2553) at r (http://localhost:52094/vendor.06aeb4c7c3d4cb244ffd.bundle.js:1376:1665) at t.compileModuleAsync (http://localhost:52094/vendor.06aeb4c7c3d4cb244ffd.bundle.js:1383:563) at e.project (http://localhost:52094/vendor.06aeb4c7c3d4cb244ffd.bundle.js:1234:672) at e.XO5T.e._tryNext (http://localhost:52094/vendor.06aeb4c7c3d4cb244ffd.bundle.js:772:11946) at e.XO5T.e._next (http://localhost:52094/vendor.06aeb4c7c3d4cb244ffd.bundle.js:772:11848) at e.next (http://localhost:52094/vendor.06aeb4c7c3d4cb244ffd.bundle.js:1059:5149) at e.RRVv.e._subscribe (http://localhost:52094/vendor.06aeb4c7c3d4cb244ffd.bundle.js:660:9655) at e.t._trySubscribe (http://localhost:52094/vendor.06aeb4c7c3d4cb244ffd.bundle.js:1206:3755) at e.t.subscribe (http://localhost:52094/vendor.06aeb4c7c3d4cb244ffd.bundle.js:1206:3584) at t.XO5T.t.call (http://localhost:52094/vendor.06aeb4c7c3d4cb244ffd.bundle.js:772:11463) at t.subscribe (http://localhost:52094/vendor.06aeb4c7c3d4cb244ffd.bundle.js:1206:3553) at t.call (http://localhost:52094/vendor.06aeb4c7c3d4cb244ffd.bundle.js:1313:6219) at t.subscribe (http://localhost:52094/vendor.06aeb4c7c3d4cb244ffd.bundle.js:1206:3553) at t.call (http://localhost:52094/vendor.06aeb4c7c3d4cb244ffd.bundle.js:1313:6219)

mikeumus · 2017-03-18T16:36:08Z

@sorakthunly, it has for me.
This fixed it:

This happens in @angular/[email protected] when doing a production build (ng build -prod) while using the compiler class in your code.

To replace the compiler you'll want to use "dynamic component creation". See this SO:

How can I use/create dynamic template to compile dynamic Component with Angular 2.0?

From my Stack Overflow answer here: http://stackoverflow.com/a/42843683/1762493

sorakthun · 2017-03-19T10:16:13Z

@mikeumus Thanks, Mike. There are a lot of answers. Which one of those works for you? Also, is this just a temporary issue for @angular/cli1.0.0-rc.2?

sorakthun · 2017-03-19T10:16:48Z

@mikeumus will revert back to rc.1 does the trick?

sherlock1982 · 2017-07-13T10:54:22Z

I'm not using compiler class but I still have this error occasionally using AngularClass seed. Now I can always reproduce on one machine with Firefox only. Other clients work as expected

mikeumus · 2017-07-13T14:43:20Z

@sorakthunly, pardon the tardy response, but going ahead in versions resolved it for me I believe.

@sherlock1982, which version of the CLI are you running for this?

GeorgeKnap · 2017-11-04T21:38:12Z

I was facing the same Runtime compiler error in AOT production build.
After a nice Saturday of rewriting project step by step I found that the problem was following module load:

export function loadGisModule() {
    return GisModule;
}

export const routes: Routes = [
    {
        path: '',
        component: OsksLayoutComponent,
        children: [
            {
                path: '',
                loadChildren: loadGisModule
            }
        ]
    }
];

@NgModule({
    imports: [
        RouterModule.forChild(routes)
    ],
    exports: [
        RouterModule
    ]
})
export class OsksLayoutRoutingModule { }

Changing module load to usual lazy load fixed the issue.
loadChildren: '../../gis/gis.module#GisModule'

I feel a bit frustrated. The error message is very bizzare. But hey. Fixed. Hope it helps to anybody.

versions>
@angular/angular: 5.0.0
@angular/cli: 1.5.0
typescript: 2.6.1

ghost · 2017-11-25T14:54:50Z

@GeorgeKnap I have the same issue. My problem is that I precisely don't want to lazy load. I wonder if I should open an issue about it.

versions:
angular 4.4.6
angular cli 1.4.9

nagarsuresh · 2017-12-11T06:39:59Z

@GeorgeKnap @guenam my problem is exactly same, I had to convert all my modules to lazy loaded modules, i am not sure what the way to load modules with routes in eager way.
Did you open any issue about it?

ghost · 2017-12-11T11:34:05Z

@snagar78 No I didn't: I had not upgrade to angular 5 yet, waiting for 5.1. Upgraded yesterday so I will test this week to see if the issue has miraculously disappeared or not. I'll report it here.

What angular version are you using btw?

dereklin · 2017-12-25T23:07:16Z

The problem exists with 5.1 as well.

I just watched a talk by Deborah on routing and discovered loadChildren for non-lazily routed modules.
https://github.com/DeborahK/MovieHunter-routing.

It's too bad it doesn't work for AOT build.

I don't want to lazy load my module. Here is what I am doing right now:

@NgModule({
  imports: [
    RouterModule.forRoot([]),
    CoreRoutingModule // All routes are set up here
  ],
  exports: [RouterModule]
})
export class AppRoutingModule { }

ghost · 2017-12-28T10:48:22Z

Just upgraded to 5.1 and, as @dereklin already indicated, the issue stays.

alfie-far · 2018-03-07T08:47:04Z

I started working with version 5.2 and the problem is still there.
I can not eager load my module.
I think our best option for now is to play with PreloadingStrategy interface in order to selectively eager load our modules.

I found below link which might be helpful. It resolved my issue for now.

Custom preloading strategy for Angular modules

DanielOrmeno · 2018-03-16T06:55:58Z

Updated You guys might want to take a look at this #4192

ghost · 2018-03-16T08:23:05Z

@DanielOrmeno I don't understand. #5460 is this page. Typo? :-)

DanielOrmeno · 2018-03-17T02:15:07Z

Yes @guenam! Thanks for pointing it out, I meant #4192, Updated.

thecyberd3m0n · 2018-04-10T00:50:24Z

how to do it (import routes) with ng-packaged module? Is it possible?

angular-automatic-lock-bot · 2019-09-08T02:41:03Z

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

mikeumus closed this as completed Mar 17, 2017

dereklin mentioned this issue Dec 25, 2017

using loadChildren for non lazily loaded modules not working on AOT build angular/angular#21170

Closed

angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error: Runtime compiler is not loaded #5460

Error: Runtime compiler is not loaded #5460

mikeumus commented Mar 16, 2017 •

edited

Loading

clydin commented Mar 16, 2017

mikeumus commented Mar 17, 2017 •

edited

Loading

sorakthun commented Mar 18, 2017

mikeumus commented Mar 18, 2017 •

edited

Loading

sorakthun commented Mar 19, 2017

sorakthun commented Mar 19, 2017

sherlock1982 commented Jul 13, 2017

mikeumus commented Jul 13, 2017 •

edited

Loading

GeorgeKnap commented Nov 4, 2017 •

edited

Loading

ghost commented Nov 25, 2017 •

edited by ghost

Loading

nagarsuresh commented Dec 11, 2017

ghost commented Dec 11, 2017

dereklin commented Dec 25, 2017 •

edited

Loading

ghost commented Dec 28, 2017

alfie-far commented Mar 7, 2018 •

edited

Loading

DanielOrmeno commented Mar 16, 2018 •

edited

Loading

ghost commented Mar 16, 2018

DanielOrmeno commented Mar 17, 2018

thecyberd3m0n commented Apr 10, 2018 •

edited

Loading

angular-automatic-lock-bot bot commented Sep 8, 2019

Error: Runtime compiler is not loaded #5460

Error: Runtime compiler is not loaded #5460

Comments

mikeumus commented Mar 16, 2017 • edited Loading

Bug Report or Feature Request (mark with an x)

Versions.

Repro steps.

The log given by the failure.

Desired functionality.

Mention any other details that might be useful.

clydin commented Mar 16, 2017

mikeumus commented Mar 17, 2017 • edited Loading

sorakthun commented Mar 18, 2017

mikeumus commented Mar 18, 2017 • edited Loading

sorakthun commented Mar 19, 2017

sorakthun commented Mar 19, 2017

sherlock1982 commented Jul 13, 2017

mikeumus commented Jul 13, 2017 • edited Loading

GeorgeKnap commented Nov 4, 2017 • edited Loading

ghost commented Nov 25, 2017 • edited by ghost Loading

nagarsuresh commented Dec 11, 2017

ghost commented Dec 11, 2017

dereklin commented Dec 25, 2017 • edited Loading

ghost commented Dec 28, 2017

alfie-far commented Mar 7, 2018 • edited Loading

DanielOrmeno commented Mar 16, 2018 • edited Loading

ghost commented Mar 16, 2018

DanielOrmeno commented Mar 17, 2018

thecyberd3m0n commented Apr 10, 2018 • edited Loading

angular-automatic-lock-bot bot commented Sep 8, 2019

mikeumus commented Mar 16, 2017 •

edited

Loading

Bug Report or Feature Request (mark with an `x`)

mikeumus commented Mar 17, 2017 •

edited

Loading

mikeumus commented Mar 18, 2017 •

edited

Loading

mikeumus commented Jul 13, 2017 •

edited

Loading

GeorgeKnap commented Nov 4, 2017 •

edited

Loading

ghost commented Nov 25, 2017 •

edited by ghost

Loading

dereklin commented Dec 25, 2017 •

edited

Loading

alfie-far commented Mar 7, 2018 •

edited

Loading

DanielOrmeno commented Mar 16, 2018 •

edited

Loading

thecyberd3m0n commented Apr 10, 2018 •

edited

Loading