misc(publish): include the report bundle in npm package

[paulirish]

to support folks like web.dev using our report renderer we need to include the new renderer API in our published assets

[connorjclark]

What's wrong with a client using lighthouse/report/renderer/report-renderer.js ? EDIT: oh, the function requires this file in the dist output. nvm

We could even provide an exports field in package.json so lighthouse/renderer would import report-renderer.js

[paulirish]

We could even provide an exports field in package.json so lighthouse/renderer would import report-renderer.js

looks good. tried it out with a local web.dev (thank you build-pack) and we're good.

esm, too. ;)

[connorjclark]

When exports is defined, it means only files that match one of these rules may be imported from the package. See the output from yarn build-devtools for how this breaks pubads:

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lighthouse-core/lib/i18n/i18n' is not defined by "exports" in /Users/runner/work/lighthouse/lighthouse/lighthouse/node_modules/lighthouse/package.json

Adding this line should fix it:

"./lighthouse-core/*": "./lighthouse-core/*"

[paulirish]

@connorjclark can we merge as is? i certainly don't want to block v9 release with a "lets lock down our node exports" exercise. We've already found that it's not trivial with just one of our many downstream customers. :(