Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Uncaught TypeError: s.JitCompilerFactory is not a constructor
See original GitHub issueBug Report or Feature Request (mark with an x)
- [X] bug report -> please search issues before submitting
- [ ] feature request
Versions.
@angular/cli: 1.5.0-beta.4 node: 6.10.3 os: win32 x64 @angular/animations: 5.0.0-rc.1 @angular/common: 5.0.0-rc.1 @angular/compiler: 5.0.0-rc.1 @angular/core: 5.0.0-rc.1 @angular/forms: 5.0.0-rc.1 @angular/http: 5.0.0-rc.1 @angular/platform-browser: 5.0.0-rc.1 @angular/platform-browser-dynamic: 5.0.0-rc.1 @angular/router: 5.0.0-rc.1 @angular/cli: 1.5.0-beta.4 @angular/compiler-cli: 5.0.0-rc.1 @angular/language-service: 5.0.0-rc.1 typescript: 2.5.3
Repro steps.
- ng build --prod
- build successfully ( no error at all )
- serve the generated bundle from node.js
- application failed to load, and the error trace below displayed in the browser console.
note. ng build (without --prod) build and load fine.
The log given by the failure.
From browser console:
vendor.1ed5b021bd13a10b4eea.bundle.js:1 Uncaught TypeError: s.JitCompilerFactory is not a constructor at r (vendor.1ed5b021bd13a10b4eea.bundle.js:1) at Je (vendor.1ed5b021bd13a10b4eea.bundle.js:1) at Ye (vendor.1ed5b021bd13a10b4eea.bundle.js:1) at Qe (vendor.1ed5b021bd13a10b4eea.bundle.js:1) at new t (vendor.1ed5b021bd13a10b4eea.bundle.js:1) at Object._n [as createNgModuleRef] (vendor.1ed5b021bd13a10b4eea.bundle.js:1) at e.create (vendor.1ed5b021bd13a10b4eea.bundle.js:1) at vendor.1ed5b021bd13a10b4eea.bundle.js:1 at t.invoke (polyfills.63ab2a039111021d7498.bundle.js:1) at Object.onInvoke (vendor.1ed5b021bd13a10b4eea.bundle.js:1)
Desired functionality.
Should build and load fine in --prod mode as well.
Mention any other details that might be useful.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Closing this issue as I finally found out that this error is actually caused by “angular2-busy” component that I’m using. Thanks!
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.