JSON module supports named import for js/esm

[JSerFeng]

JSON module supports named import only for js/auto but not for js/esm.

If user imports json with import attributes, then json module should only provide default export which should follow the spec.

If user not using import attribute, then json module is capable to provide named exports even for js/esm

How do you think @alexander-akait

[xiaoxiaojx]

I checked that webpack currently only supports exporting via export default. Since we have the spec now, any new code should ideally align with it. @hai-x What do you think?

ERROR in ./src/index.js 3:12-16
Can't import the named export 'main' (imported as 'main') from default-exporting module (only default export is available)

webpack 5.101.3 compiled with 1 error in 56 ms

[JSerFeng]

I think the spec for ESM importing json module is for import attribute, seems no spec tells how normal import without attributes behaves.

If we treat JSON module as special commonjs module, the commonjs module can have named exports if export symbols can be statically analyzed.

The point is should we treat normal JSON imports the same as import attribute type: 'json' ?

What I want is

• For import attribute with json type, export default only
• Otherwise supports named exports

[alexander-akait]

@JSerFeng You are right, we introduce JSON support when we don't have spec at all for import attributes and babel (other transpilers/bundlers) supports named exports too, and to support old modules (where JSON was imported using named import) we are allowing to do it but not recommended, anyway yes, for with { type: 'json' } we should not support named exports

Do you want to send a fix?

[JSerFeng]

I'll make one fix