[PR WELCOME] Discover primary and secondary entry points from user configuration

Type of Issue

[ ] Bug Report
[x] Feature Request

Description

Historically, a package.json and a ng-package.json are used to “configure” ng-packagr. The package.json is used for the module ID, npm metadata, and more node/npm-related things. The ng-package.json is used for destination paths, finding the entry file of an entry point, and angular/typescript/rollup-specific things.

Entry point discovery should be changed, see below. Discovery of primary and secondary entry points should both use this.

Expected Behaviour

New Draft / Outline (first one “wins”):

• package.json: ngPackage
• ng-package.json (requires a package.json as sibling)
• ng-package.js (default export, requires a package.json as sibling)

Note: ignore package.json w/o ngPackage property.

Version Information

ng-packagr: v2.0.0-rc.0

[gnomeontherun]

I personally don’t like adding stuff into package.json files. I don’t have a problem with specific files for specific tools, because things stay organized and don’t overload another file.

Having a ng-package.js type config file would be great should there be a need to write configuraiton/plugin type values, like what webpack does. For example, what if I wanted to write additional logic to copy files or something pre/post bundling, perhaps you could provide hooks during the build lifecycle to run tasks. Just a thought.

[github-actions[bot]]

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.}