Ambiguous Package Name

We stumbled upon the issue of ambiguous imports when using this library.
`require(assert)` can refer to the library or Node's assert API.

It would be awesome to have the library available under a second name (e.g., `assert.js`) in use cases where you don't want to have this ambiguity. Other libraries with the same issue went down a similar road, e.g. [punycode](https://www.npmjs.com/package/punycode.js).

Original thread: https://github.com/sindresorhus/eslint-plugin-unicorn/issues/2326

Start by inspecting the package metadata, published entry points, and how the current require('assert') name is exposed. Determine how a second name such as assert.js could be published without disrupting the existing name; done means the alternate package name is available and the ambiguity is resolved.

Written by the indexing model from the issue text.