html-formatter: fix when installed locally to node project

[davidjgoss]

Summary

Fixes the @cucumber/html-formatter CLI when the package is installed as a project dependency (rather than only working when installed globally).

Details

Installing to a project like npm i @cucumber/html-formatter and then running in an npm script would currently yield an error like:

[Error: ENOENT: no such file or directory, open '/Users/davidgoss/Documents/Projects/html-formatter-test/node_modules/@cucumber/html-formatter/dist/src/../../node_modules/@cucumber/react/dist/src/styles/cucumber-react.css'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/Users/davidgoss/Documents/Projects/html-formatter-test/node_modules/@cucumber/html-formatter/dist/src/../../node_modules/@cucumber/react/dist/src/styles/cucumber-react.css'
}
npm ERR! Test failed.  See above for more details.

This is due to the relative path to the cucumber react CSS file - this breaks when installed as a dependency, because our own dependencies are usually hoisted up to the node_modules of the host project.

This changes to use a reliable function to resolve the path to the @cucumber/react package so it works in global or local context.

Types of changes

• Bug fix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist:

• The change has been ported to Java.
• The change has been ported to Ruby.
• The change has been ported to JavaScript.
• The change has been ported to Go.
• The change has been ported to .NET.
• I've added tests for my code.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have updated the CHANGELOG accordingly.

[davidjgoss]

Actually realised I'll need to do some changes here for cucumber/cucumber-js#1425, so will pick that up on this branch too.

[aslakhellesoy]

Awesome - thanks @davidjgoss !