Fix Jest test mocks

[facuacostag]

Issue

Version 4.3.0 changed how files were exported in the package.json as you can see in this commit. If you were mocking the library on Jest so tests could pass, the new configuration wasn't allowing Jest to find the package to be mocked.

Solution

Adding require to to each of the exports solves the issue and allows Jest to work again.

[facuacostag]

@microsoft-github-policy-service agree

[EleryanYuri]

Hello,

My team is facing issue that this PR would solve.
We have a really strict policy about code coverage and being unable to mock the package is a really painfull

Thanks for providing it and I hope this will be soon taken into account.

[Copilot]

Pull Request Overview

Adds a CommonJS entry point to the package exports so Jest can correctly mock the library.

• Adds a require mapping under the root export to point to the CJS build.
• Ensures Jest can resolve the module when running tests.

[Copilot]

The ./manual export block currently only defines types. You should add a require mapping (e.g., "require": "./dist/manualIndex.js") so Jest can resolve the CommonJS path for the manual entry as well.

[Karlie-777]

#78