Is --create-ivy-entry-points correctly used?

Current Behavior

Currently this script is added

“postinstall”: “ngcc --properties es2015 browser module main --first-only --create-ivy-entry-points”,

when adding something from @nrwl/angular.

However I just noticed this

… If you opt-out of bundling dependencies you will need to run the standalone Angular compatibility compiler (ngcc). This is needed because otherwise Node will be unable to resolve the Ivy version of the packages.

You can run ngcc after each installation of node_modules by adding a postinstall npm script:

// package.json
{
  "scripts": {
    "postinstall": "ngcc"
  }
}

Don’t use --create-ivy-entry-points as this will cause Node not to resolve the Ivy version of the packages correctly.

source

So I was wondering if it being there is correct?

[BruneXX]

Hi Guys is not clear to me after read all thread if I need to continue using

ngcc --properties es2015 browser module main --first-only --create-ivy-entry-points

or just:

ngcc

I’m came here after reading the following: Don’t use --create-ivy-entry-points as this will cause Node not to resolve the Ivy version of the packages correctly.

from the angular documentation https://angular.io/guide/ivy but is not clear to me what I need to do in the latest angular version (11.0.4)

Please can anyone clarify?

Thanks!

[ranyehushua]

@brandonroberts I am having trouble understanding, so you are saying that running "postinstall": "ngcc --properties es2015 browser module main --first-only --create-ivy-entry-points" is still permissible? or are you saying we should follow the docs and not run with the --create-ivy-entry-points flag? Thanks very much!