Using npm's experimental ESM branch of Node.js I took 30 minutes to hack together a WASM loader and now I can `import "./foo.wasm"` and it just works! https://gist.github.com/iarna/8e06ef125a69dfa7d1b65a6daf44a190 …pic.twitter.com/n6fx5LysVx
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Would be nice if that loader could be ad-hoc standardized and enabled by default. Then people could just import WASM files and didn't need to worry about WASM loaders at all (similar to how JSON is already supported by CJS implementations)
I hear @linclark is working on standardizing this.
Initial thoughts: Great for devving, testing. However I'd very much rely on the capabilities of a bundler to optimize how was will stream compile/instantiate for performance etc. In addition to our future capabilities to dive into the .wat format and tree shake, hoist wasm
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.