[_] add inlineOnly

[TamaraFinogina]

Description

Fix npm warning to enable release

Checklist

• Changes have been tested locally.
• Unit tests have been written or updated as necessary.
• The code adheres to the repository's coding standards.
• Relevant documentation has been added or updated.
• No new warnings or errors have been introduced.
• SonarCloud issues have been reviewed and addressed.
• QA Passed

Testing Process

unit tests

[TamaraFinogina]

Not sure if it's better to make 'hash-wasm' external or bundle it

[larryrider]

what is the difference between them? (pros vs cons)

[TamaraFinogina]

As I get it: one is clean, and has no external dependencies (current one), another is (with hash-wasm made external) will require any library that uses internxt-crypto to install hash-wasm as a dependency. In theory the second way can prevent double loading and be easier if different builders are used. But not sure

[CandelR]

I will left it bundled in order to avoid future incompatible issues in different hash-wasm versions (as we have in crypto-js in another projects with 4.2 and <4.2.
Also I think better to change inlineOnly, InlineOnly: false silences the warning, if another dep is bundled in the future, there will be nothing to detect it.
A more robust alternative would be: inlineOnly: [“hash-wasm”]
This also removes the warning, but also acts as a whitelist, if any other node_modules package is accidentally bundled, tsdown will throw an error in the build

[larryrider]

i see, lets let it bundle and we'll see

[TamaraFinogina]

@CandelR @larryrider Done

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud