Modify library package.json (do not copy to dist folder)

Type of Issue

[ ] Bug Report
[x] Feature Request

Description

Do not copy/write an additional package.json in the dist directory.

Current Behaviour

package.json is copied from source folder to dist folder.

Publish workflow is cd dist && npm publish

Expected Behaviour

package.json is validated whether generated artefacts are references (properties main, typings, and so on). If properties in package.json are missing (or pointing to wrong location), package.json will be updated with correct properties.

Optionall, an .npmignore files is generated to exclude source files from the npm package.

Publish workflow is npm publish in current working directory.

Library package.json would look like:

{
  "name": "@foo/bar",
  "version": "1.0.0",
  "typings": "./dist/typings/foo-bar-api.d.ts",
  "main": "./dist/<path-to-js-bundle>",
  "module": "./dist/<path-to-js-bundle>",
  /* .. */
}

Secondary entry point package.json would also need to be validated and updated. Example would look:

{
  "name": "@foo/bar/bla/blubb",
  "typings": "../../dist/typings/foo-bar-api.d.ts",
  "main": "../../dist/<path-to-js-bundle>",
  "module": "../../dist/<path-to-js-bundle>",
  /* .. */
}

Version Information

ng-packagr: 6.x

[nategreen]

My 2 cents as I’m more familiar with Node/npm than with Angular (and not an expert in either one): I would at least like to see this be an option.

I tend to agree with lerna’s maintainer, that compiling to a separate/duplicate package seems like a Node/npm anti-pattern—even if that’s debatable, compiling to a separate place/package could be said to be an opinionated workflow, right?

From my perspective, trying to set up a design system with Angular components but also other, non-Angular npm packages, it seems like that opinionated piece is what’s making it hard to get everything up and running. Since ng-packagr and Angular CLI are ostensibly the bridge between an Angular-formatted project and a Node/npm-formatted package…I would (and did) expect to be able to use other Node/npm tools like lerna to work with the resulting packages, without all the fiddling/working-around that’s currently required. Again, just my 2 cents, though, and I’m certainly not an authority on Angular, lerna, NPM, or any of it.

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