To Expose or Not To Expose Configuration for tsc, ngc, rollup about ng-packagr HOT 3 CLOSED

Personally, imho, I'll go with 2 (two!).

Drawback: adding more configuration requires a new version of ng-packagr to be released, supporting the new config options.

Relevant config options are imho:

• files for tsc (the entry file, which in reality becomes publicApiEntry as string value for a single file rather than "files": [] array with tsc)
• flatModuleOutFile (for ngc, value could even be inferred by library name and public entry file)
• external, globals, banner, moduleName for rollup (moduleName could even by inferred by library name)

from ng-packagr.

see the ng-package.schema.json file.

it is schema for supported config file format.

we'll try to hide the internal tools as-much-as-possible and rather have a lib object in configuration that describes the structure of the library being built. the internal configs of tsc and friends than need to follow what comes in.

from ng-packagr.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

_{This action has been performed automatically by a bot.}

from ng-packagr.