See whatwg/html#4943, it appears this is due to lack of consensus between browsers based on a security concern. It does not seem to imply that they won't be implemented in future.
Given that we have erred on the side of web compatibility so far in the implementation, I would like to suggest we bring back the --experimental-json-modules flag for Node.js as we unflag modules to indicate the stability of the feature.
For example, were JSON modules to reland but with slightly different semantics (eg import json from './file.json' as json has been proposed or similar), then that keeps the door open for Node.js to be able to share in any new semantics.
See whatwg/html#4943, it appears this is due to lack of consensus between browsers based on a security concern. It does not seem to imply that they won't be implemented in future.
Given that we have erred on the side of web compatibility so far in the implementation, I would like to suggest we bring back the
--experimental-json-modulesflag for Node.js as we unflag modules to indicate the stability of the feature.For example, were JSON modules to reland but with slightly different semantics (eg
import json from './file.json' as jsonhas been proposed or similar), then that keeps the door open for Node.js to be able to share in any new semantics.