fix(#593): properly resolve the path to webpack loaders

[m5r]

Description

use require.resolve to get the proper path to the webpack loader

#593

Code review items

• Readable: Concise, well named, follows the style guide, documented if necessary.
• Documented: Configuration and user documentation on cht-docs
• Tested: Unit and/or integration tests where appropriate
• Backwards compatible: Works with existing data and configuration. Any breaking changes documented in the release notes.

License

The software is provided under AGPL-3.0. Contributions to this project are accepted under the same license.

[m5r]

@jkuester could you review this fix? With this deployed, we can upgrade CHT core to use CHT conf 3.22
It will fix the couple of integration and e2e tests that were failing after upgrading to 3.21

[jkuester]

👍 I was unable to repro the error, but that may be related to the version of cht-core I was using to test with. Either way, this branch works fine for me and based on my reading of using require.resolve in your webpack config seems to be that it is recommended anyway....

[medic-ci]

🎉 This PR is included in version 3.21.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀