add --preserve-extensions option

[WickyNilliams]

• added option --present-extensions which keeps .js extensions
  • handles exports
  • handles typesVersions
  • handles wrappers
• add test
• fixed up some jsdoc types which were incorrect
• small typo fix "nain" -> "main"

[WickyNilliams]

i used for..in here because i was getting inconsistent ordering between test runs when using Object.entries and Object.fromEntries and i think this should preserve order

[WickyNilliams]

actually, i am still getting inconsistent results. it fails about 50% of the time. there must be some kind of race condition or shared state between test runs 🤔

it's always the same failure when it happens, these two exports entries end up swapped around. but which test fails also varies. very strange

  -         "./components/a.js": {
  -             "default": "./tests/module/components/a/a.js"
  +         "./components/b.js": {
  +             "default": "./tests/module/components/b/b.js"
            },
  -         "./components/b.js": {
  -             "default": "./tests/module/components/b/b.js"
  +         "./components/a.js": {
  +             "default": "./tests/module/components/a/a.js"

[WickyNilliams]

even running the tests in serial (-s flag in ava) i get this issue. not sure what the cause is

[WickyNilliams]

I wonder if there is an opportunity to simplify typesVersions by following this kind of wildcard approach described here or here, so that you don't need to list every type location.

I don't know much about how typesVersions works, so perhaps there isn't. But thought i would ask!

[UpperCod]

Hi @WickyNilliams , great PR! I have refactored the workspaces for testing, deprecating the use of ava and switching to node:test. Now it offers the following benefits:

1. Matching based on specific files.
2. Each test is a package, so you can associate specific dependencies for the test, such as TypeScript + @atomico/exports.

Now, upon reviewing the output, I noticed this type of output:

exports/tests/packages/test-2/package.tmp.json

Line 24 in 6a1a6a5

".js": {

If the index is equal to ".js", we should transform it to "."

[UpperCod]

I wonder if there is an opportunity to simplify typesVersions by following this kind of wildcard approach described here or here, so that you don't need to list every type location.

I don't know much about how typesVersions works, so perhaps there isn't. But thought i would ask!

The adoption of package.json#exports makes me wonder if it's time to deprecate typesVersions.

(By the way, I didn't intend to close the PR; it was a clicking error while typing on my phone.)