Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support serving wasm with application/wasm #7670

Merged
merged 1 commit into from Mar 9, 2018

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Mar 8, 2018

Backport of #7664


The fastest way to load wasm is WebAssembly.instantiateStreaming but it requires the mime-type to be correct.

I can't update the mime module because it has engines >=6.

I updated broccoli-middleware but have to manually define it for testem.

(cherry picked from commit 43400c3)

The fastest way to load wasm is WebAssembly.instantiateStreaming
but it requires the mime-type to be correct.

I can't update the mime module because it has engines >=6.

I updated broccoli-middleware but have to manually define it for testem.

(cherry picked from commit 43400c3)
@krisselden
Copy link
Contributor

There seems to be some yarn cache issue on Appveyor on one of the node versions in the matrix, I'm pretty sure this PR is good.

[1/5] Validating package.json...
32[2/5] Resolving packages...
33[3/5] Fetching packages...
34error Couldn't find a package.json file in "C:\\Users\\appveyor\\AppData\\Local\\Yarn\\cache\\v1\\npm-ajv-5.2.2-47c68d69e86f5d953103b0074a9430dc63da5e39"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants