__extends is not defined
See original GitHub issueUsing the install instructions, and adding the module to imports or the providers causes this error:
Uncaught ReferenceError: __extends is not defined(…)
If I click on the file where the error is occurring it shows this:
var PropertyGroup = (function (_super) {
__extends(PropertyGroup, _super); <<<this line
function PropertyGroup() {
_super.apply(this, arguments);
this.properties = null;
}
...etc
Am I missing something?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:7
Top Results From Across the Web
[BUG] Uncaught ReferenceError: __extends is not defined
I have a react app which is created with create-react-app. ... The problem exists only when app is build for production. It's working...
Read more >ReferenceError: extend is not defined - Stack Overflow
You've tagged jquery so I'm presuming your using jquery. extend isn't a built in method to javascript but JQuery has a method called...
Read more >extends - JavaScript - MDN Web Docs - Mozilla
The extends keyword is used in class declarations or class expressions to create a class that is a child of another class.
Read more >[BUG] Uncaught ReferenceError: __extends is not defined
Description/Screenshot I have a react app which is created with create-react-app. When I create production build of my app and serve it I'm ......
Read more >ReferenceError: exports is not defined in TypeScript | bobbyhadz
If you run your code in the browser, try removing the module property from your tsconfig.json file and set target to es6 ....
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 FreeTop 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
Top GitHub Comments
fixed in 1.0.0-alpha.31
Just because we moved to Angular CLI 2 days ago and we haven’t released on npm yet. Sorry for that, I publish it right now.