Skip to content

[es2015] Constructor don't call super #10193

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mantyz opened this issue Apr 5, 2018 · 5 comments
Closed

[es2015] Constructor don't call super #10193

mantyz opened this issue Apr 5, 2018 · 5 comments
Assignees

Comments

@mantyz
Copy link

mantyz commented Apr 5, 2018

Versions

Angular CLI: 6.0.0-rc.1
Node: 8.11.1
OS: linux x64
Angular: 6.0.0-rc.1
... animations, cli, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router


@angular-devkit/architect: 0.5.1
@angular-devkit/build-angular: 0.5.1
@angular-devkit/build-optimizer: 0.5.1
@angular-devkit/core: 0.5.1
@angular-devkit/schematics: 0.5.1
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 6.0.0-rc.1
@schematics/angular: 0.5.1
@schematics/update: 0.5.1
typescript: 2.7.2
webpack: 4.5.0
Linux (Debian 8)

Repro steps

  • ng new project
  • change tsconfig.json target to es2015
  • ng serve --prod
  • run localhost:4200
  • open browser DevTools console

Observed behavior

bug

Desired behavior

I want to see the demo page, but I see an error in the console.

Mention any other details that might be useful (optional)

@filipesilva
Copy link
Contributor

I think this happens because Build Optimizer does not support ES2015 yet. This is something we mean to support. Meanwhile you can turn off Build Optimizer in your production configuration in the angular.json file.

@markgoho
Copy link
Contributor

@filipesilva is there any urgency to fixing this? Or is it like if we set the output to es6 then it's already "optimized" and we're not losing much by not having Build Optimizer.

@filipesilva
Copy link
Contributor

Heya, just wanted to mention that we are tracking this problem in angular/devkit#816.

@markgoho I don't have an exact timeframe but it is definitely a 6.x concern.

@jmpreston
Copy link

jmpreston commented Jul 6, 2018

It only took 6 hours of troubleshooting to find this thread but in the angular.json file this works:
"buildOptimizer": false,

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants