feat: Fix interop with cjs-module-lexer

[benasher44]

This moves the main validator exports to validator-main.js (avoid conflict with top-level validator.js when running build), which then allows both a default and named exports in the index by re-exporting. By doing this, we get a CJS validator that also can be name-imported in node ESM.

Checklist

• PR contains only changes related; no stray files, etc.
• README updated (where applicable)
• Tests written (where applicable)
• References provided in PR (where applicable)

[benasher44]

Well I got pretty far just with this small change, but now I can't figure out how to get the AMD test to pass… any pointers there?

[benasher44]

I also tried without adding a file to re-export from + just copy pasting all of the exports in the default export as named exports, but that has the same issue (seemingly) breaking AMD.

[WikiRik]

When building babel does give a warning;

Using named and default exports together. Consumers of your bundle will have to use validator['default'] to access the default export, which may not be what you want. Use `exports: 'named'` to disable this warning

That's also what seems to be changed in the built files. Apart from the expected additional exports it also returned validator before but now that's part of exports['default']. Unfortunately I have no experience with AMD to help out further

[benasher44]

No problem. Thanks anyway! Yeah that's what I discovered as well. I did all kinds of inspection there and couldn't figure out a different way to get to the original module object shape it was expecting before :(

[WikiRik]

Might just be a Babel thing. I know there is an outdated PR from one of the maintainers that tried to overhaul the config (also because we're on old versions of Babel and Rollup); #1869

Maybe a smaller version of that is the way to go, but merging PRs is often quite slow with the current maintainers, see #2376

[benasher44]

It could be, but in my local build, I tried with the latest version of Babel 8, which didn't change anything.

[profnandaa]

I'll take a look at this while on my dev machine. But this is not a disruptive change like what I've seen in the past. Happy to see this land once all t's are crossed.

[benasher44]

@profnandaa any chance you'll have time to look soon?

[kojang123]

Bisakah aplikasi crome itu di perketat suapaya kalaw saya main slot engine tidak kalah tolong dibantu

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (9ff3424) to head (f760902).

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #2377   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          114       115    +1     
  Lines         2599      2598    -1     
  Branches       658       659    +1     
=========================================
- Hits          2599      2598    -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[benasher44]

@profnandaa @WikiRik finally got this working in a backward compatible / sustainable way. mind taking another look?