fix: JSON modules disable named exports

[JLHwung]

Description

This is a follow-up to #13031, see that PR for the rationale. I searched assert { type: "json" } in our codebase and replaced all named imports, please let me know if I have missed any. Thank you.

Checklist

• I’ve added tests to confirm my change works.
• (If changing the API or CLI) I’ve documented the changes I’ve made (in the docs/ directory).
• (If the change is user-facing) I’ve added my changes to changelog_unreleased/*/XXXX.md file following changelog_unreleased/TEMPLATE.md.
• I’ve read the contributing guidelines.

✨Try the playground for this PR✨

[fisker]

Can you revert this one? So we can have one test for named export.

[JLHwung]

I could preserve this test as-is, but for the same reason mentioned in #13035, this test will block babel/babel#14668 because that PR proposes to align Babel's behaviour with Node.js and the spec. To recap, in that PR Babel will forbid export { foo } from a JSON module, so the test will be passing (incorrectly) on older Babel versions and throwing (expectedly) on latest versions.

I suggest we add export { foo } and other tests after babel/babel#14668 is landed.

BTW technically, export { default as foo } is still a named export.

[fisker]

Okay, thanks for the explanation.