Various warnings when bundling with CRA

[OR13]

./node_modules/@transmute/did-key-bls12381/node_modules/@mattrglobal/bbs-signatures/lib/wasm.js
Critical dependency: the request of a dependency is an expression

./node_modules/@transmute/did-key-bls12381/node_modules/@mattrglobal/node-bbs-signatures/lib/bls12381.js
Critical dependency: the request of a dependency is an expression

./node_modules/@transmute/did-key-bls12381/node_modules/@mattrglobal/node-bbs-signatures/lib/bls12381toBbs.js
Critical dependency: the request of a dependency is an expression

./node_modules/@transmute/did-key-bls12381/node_modules/@mattrglobal/node-bbs-signatures/lib/bbsSignature.js
Critical dependency: the request of a dependency is an expression

./node_modules/@mattrglobal/node-bbs-signatures/lib/bls12381.js
Critical dependency: the request of a dependency is an expression

./node_modules/@mattrglobal/node-bbs-signatures/lib/bls12381toBbs.js
Critical dependency: the request of a dependency is an expression

./node_modules/@mattrglobal/node-bbs-signatures/lib/bbsSignature.js
Critical dependency: the request of a dependency is an expression

[tplooker]

An easier way to replicate this issue is by running the basic browser sample, for some reason web-pack is insisting on installing the optional dependency of node-bbs-signatures that is for when a consumer of bbs-signatures is running in Node and would like the performance boost of executing via a native node module. I thought by specifying a seperate index.js for browser this issue would have been resolved however it appears node-bbs-signatures is still being brought in somehow.

[kdenhartog]

Seems like based on the documentation the browser property in the package.json file is a hint rather than an indicator of picking up only certain files. Maybe that has something to do with it?

https://docs.npmjs.com/cli/v7/configuring-npm/package-json#browser