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

fix(Server): Workaround for .wasm file mime type (#1575) #1580

merged 3 commits into from Dec 5, 2018


Copy link

@samsam2310 samsam2310 commented Nov 27, 2018

  • This is a bugfix
  • This is a feature
  • This is a code refactor
  • This is a test update
  • This is a docs update
  • This is a metadata update

For Bugs and Features; did you add new tests?


Motivation / Use-Case

fixes #1575

Breaking Changes


Additional Info

Copy link

@jsf-clabot jsf-clabot commented Nov 27, 2018

CLA assistant check
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

Copy link

@alexander-akait alexander-akait left a comment

Good job, thanks!

Copy link

@alexander-akait alexander-akait commented Nov 27, 2018

Please accept CLA

Copy link
Contributor Author

@samsam2310 samsam2310 commented Nov 27, 2018

I have accepted but the licence/cla seems still in pending ?

Copy link

@codecov codecov bot commented Nov 27, 2018

Codecov Report

Merging #1580 into master will increase coverage by 0.03%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1580      +/-   ##
+ Coverage   74.02%   74.06%   +0.03%     
  Files          10       10              
  Lines         670      671       +1     
+ Hits          496      497       +1     
  Misses        174      174
Impacted Files Coverage Δ
lib/Server.js 81.42% <100%> (+0.05%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7a3a257...c028b81. Read the comment docs.

Copy link

@alexander-akait alexander-akait commented Nov 27, 2018

@samsam2310 CLA sometimes buggy, will be shipped in near future

Copy link

@odinho odinho commented Dec 4, 2018

@samsam2310 If you rebase onto newest master, the Travis tests should pass.

@alexander-akait alexander-akait merged commit fadae5d into webpack:master Dec 5, 2018
5 checks passed
matheus1lva pushed a commit to matheus1lva/GrCartuchos that referenced this issue Dec 21, 2018
## The devDependency [webpack-dev-server]( was updated from `3.1.10` to `3.1.11`.
This version is **not covered** by your **current version range**.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.


<summary>Release Notes for v3.1.11</summary>

<p><a name="user-content-3.1.11"></a></p>
<h2><a href="">3.1.11</a> (2018-12-21)</h2>
<h3>Bug Fixes</h3>
<li><strong>bin/options:</strong> correct check for color support (<code>options.color</code>) (<a href="" data-hovercard-type="pull_request" data-hovercard-url="/webpack/webpack-dev-server/pull/1555/hovercard">#1555</a>) (<a href="">55398b5</a>)</li>
<li><strong>package:</strong> update <code>spdy</code> v3.4.1...4.0.0 (assertion error) (<a href="" data-hovercard-type="issue" data-hovercard-url="/webpack/webpack-dev-server/issues/1491/hovercard">#1491</a>) (<a href="" data-hovercard-type="pull_request" data-hovercard-url="/webpack/webpack-dev-server/pull/1563/hovercard">#1563</a>) (<a href="">7a3a257</a>)</li>
<li><strong>Server:</strong> correct <code>node</code> version checks (<a href="" data-hovercard-type="pull_request" data-hovercard-url="/webpack/webpack-dev-server/pull/1543/hovercard">#1543</a>) (<a href="">927a2b3</a>)</li>
<li><strong>Server:</strong> mime type for wasm in contentBase directory (<a href="" data-hovercard-type="issue" data-hovercard-url="/webpack/webpack-dev-server/issues/1575/hovercard">#1575</a>) (<a href="" data-hovercard-type="pull_request" data-hovercard-url="/webpack/webpack-dev-server/pull/1580/hovercard">#1580</a>) (<a href="">fadae5d</a>)</li>
<li>add url for compatibility with webpack@5 (<a href="" data-hovercard-type="issue" data-hovercard-url="/webpack/webpack-dev-server/issues/1598/hovercard">#1598</a>) (<a href="" data-hovercard-type="pull_request" data-hovercard-url="/webpack/webpack-dev-server/pull/1599/hovercard">#1599</a>) (<a href="">68dd49a</a>)</li>
<li>check origin header for websocket connection (<a href="" data-hovercard-type="pull_request" data-hovercard-url="/webpack/webpack-dev-server/pull/1603/hovercard">#1603</a>) (<a href="">b3217ca</a>)</li>

<p>The new version differs by 9 commits.</p>
<li><a href=""><code>ff2874f</code></a> <code>chore(release): 3.1.11</code></li>
<li><a href=""><code>b3217ca</code></a> <code>fix: check origin header for websocket connection (#1603)</code></li>
<li><a href=""><code>68dd49a</code></a> <code>fix: add url for compatibility with webpack@5 (#1598) (#1599)</code></li>
<li><a href=""><code>fadae5d</code></a> <code>fix(Server): mime type for wasm in contentBase directory (#1575) (#1580)</code></li>
<li><a href=""><code>7a3a257</code></a> <code>fix(package): update <code>spdy</code> v3.4.1...4.0.0 (assertion error) (#1491) (#1563)</code></li>
<li><a href=""><code>1fe82de</code></a> <code>ci(travis): Node 11 (on OS X) crashes, use 10 for now (#1588)</code></li>
<li><a href=""><code>55398b5</code></a> <code>fix(bin/options): correct check for color support (<code>options.color</code>) (#1555)</code></li>
<li><a href=""><code>927a2b3</code></a> <code>fix(Server): correct <code>node</code> version checks (#1543)</code></li>
<li><a href=""><code>fa96a76</code></a> <code>chore(PULL_REQUEST_TEMPLATE): allow features (#1539)</code></li>
<p>See the <a href="">full diff</a></p>

  <summary>FAQ and help</summary>

  There is a collection of [frequently asked questions]( If those don’t help, you can always [ask the humans behind Greenkeeper](


Your [Greenkeeper]( bot 🌴
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

4 participants