proposal-asset-references VS proposal-import-assertions

No no, this is about things like importing WASM through the `import` keyword, or referencing assets statically through syntax:

Asset References: https://github.com/tc39/proposal-asset-references

https://github.com/tc39/proposal-asset-references is interesting. Not sure it fits with Go though.

SO, you're using webpack to support CSS imports here, BUT, did you know that you can do this in vanilla JS without webpack using something called import assertions:

This could be implemented as an import assertion[1]:

import foo from 'http://example.com/foo' assert { sha256sum: '...' }

This feature would even be useful in the web platform in general. Along with an assertion for importing plain text files (not just JSON files).

[1]: https://github.com/tc39/proposal-import-assertions

Worth noting that Import Assertions were downgraded to stage 2 from stage 3. The proposal page may continue to say "stage 3" until it can be updated.

Import Assertions: Proposal for syntax to import ES modules with assertions

Also, I'm not sure how that'd work with import assertions. That'd add another round of questions.

Hi, there is a way to import json file like:

If you want the real thing, you're looking for import assertions.

But it's still only a proposal, currently at stage 3 (which means it's almost finalised, pending any critical feedback or refinements, before it gets implemented). You can view the import assertions proposal on GitHub.

I wouldn't use import assertions in any browser since they are still a stage 3 proposal so any browser which implements them is doing before it is standardized and shouldn't be relied upon for anything that matters.

There's an issue for that to be added as aprt of import assertions https://github.com/tc39/proposal-import-assertions/issues/11...