title: lerna publish and npm pack failing to package all the files in "dist" folder
body: <p>I am trying to build my first Angular Component package using lerna and it was working pretty well until I realized I had to add "ng-packagr" to get all of the HTML bundled inline with the rest of the code. After adding that support and getting it to work now all of a sudden my files are not getting published into the tarball.</p>
  
  <p>Here is my package.json</p>
  
  <pre><code>{
    "name": "@custom/core",
    "version": "0.0.7",
    "description": "Test",
    "main": "./dist/bundles/custom-core.umd.min.js",
    "module": "./dist/esm2015/custom-core.js",
    "typings": "./dist/index.d.ts",
    "$schema": "./node_modules/ng-packagr/package.schema.json",
    "ngPackage": {
      "lib": {
        "entryFile": "./src/index.ts"
      },
      "whitelistedNonPeerDependencies": [
        "."
      ]
    },
    "scripts": {
      "build": "ng-packagr -p package.json"
    },
    "files": [
      "dist"
    ],
  ...
  </code></pre>
  
  <p>My dist folder contains all kinds of folders like this:</p>
  
  <p><a href="https://i.stack.imgur.com/cTpat.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/cTpat.png" alt="enter image description here"></a></p>
  
  <p>But then when I run a <code>lerna publish</code> or <code>npm pack</code> this is what happens:</p>
  
  <p><a href="https://i.stack.imgur.com/5BGhE.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/5BGhE.png" alt="enter image description here"></a></p>
  
  <p>As you can see only 1 file gets added to the tarball...</p>
  
  <p>Does anyone know why this is happening all of a sudden? I've tried playing around with my .gitignore thinking maybe it was forcing the packaging to ignore these other files but it wasn't that.</p>
  
  <p><strong>UPDATE</strong></p>
  
  <p>Ok so I found that the culprit is <code>ng-packagr</code>.  When I run my <code>npm run build</code> which uses <code>ng-packagr -p package.json</code> to build the different module packages, that CLI is also generating a package.json that goes inside of my <code>dist</code> folder. When the <code>npm pack</code> or <code>lerna publish</code> attempt to package everything using a <code>package.json</code> they must be looking at the generated on in <code>dist</code> rather than the one in the folder above it.</p>
  
  <p>I'm not sure how I should be fixing this.</p>