Skip to content

Add option to keep $$_gendir around for debugging purposes.  #6203

@samartioli

Description

@samartioli

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [X] feature request

Versions.

$ ng --version
@angular/cli: 1.0.1
node: 7.9.0
os: darwin x64
@angular/animations: 4.1.0
@angular/common: 4.1.0
@angular/compiler: 4.1.0
@angular/core: 4.1.0
@angular/forms: 4.1.0
@angular/http: 4.1.0
@angular/material: 2.0.0-beta.3
@angular/platform-browser: 4.1.0
@angular/platform-browser-dynamic: 4.1.0
@angular/router: 4.1.0
@angular/cli: 1.0.1
@angular/compiler-cli: 4.1.0

OSX 10.12.4

Repro steps.

Any ng command line failure

The log given by the failure.

For instance:

ERROR in src/$$_gendir/app/core/core.module.ngfactory.ts (308,7): Supplied parameters do not match any signature of call target.

ERROR in src/$$_gendir/app/app.module.ngfactory.ts (355,7): Supplied parameters do not match any signature of call target.

Desired functionality.

I am not able to access $$_gendir to begin an investigation as to what may be the issue. In this particular case, I discovered that I needed to declare a parameter, even though I wasn't using it, for AOT.

It would be great it ng had a flag to keep the intermediate build dir around for inspection.
Maybe --keep-gendir

Mention any other details that might be useful.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P5The team acknowledges the request but does not plan to address it, it remains open for discussioneffort1: easy (hours)featureIssue that requests a new feature

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions