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 for #6720: HMR not working in Firefox if proxy option present #7318

Closed
wants to merge 17 commits into from
Closed

Fix for #6720: HMR not working in Firefox if proxy option present #7318

wants to merge 17 commits into from

Conversation

dmile
Copy link
Contributor

@dmile dmile commented Jul 4, 2019

Original issue: #6720
Root cause: sockjs/sockjs-client#474 (comment)
This is a PR for naive idea how to fix it: #6720 (comment)

Copy link
Contributor

@mrmckeb mrmckeb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just one small suggestion to the comment.

packages/react-dev-utils/WebpackDevServerUtils.js Outdated Show resolved Hide resolved
Co-Authored-By: Brody McKee <mrmckeb@users.noreply.github.com>
@mrmckeb
Copy link
Contributor

mrmckeb commented Jul 28, 2019

Hi @dmile, I can see the CI has a lot of failures here. Can you try rebasing and pushing again? Thanks!

@mrmckeb mrmckeb self-assigned this Jul 28, 2019
JESii and others added 12 commits July 28, 2019 16:29
Co-Authored-By: Ian Schmitz <ianschmitz@gmail.com>
* Attempt at fixing CI issue on windows

* Try to debug why verdaccio isn't in the ps output

* Just remove the kill call alltogether
This closes #7359 by making IMAGE_INLINE_SIZE_LIMIT=0 actually disable image inlining.

We use url-loader's `limit` option to set the line at which images will be inlined, and we basically expose this option to our end users via the IMAGE_INLINE_SIZE_LIMIT environment variable. Most people using it want to disable inlining images all together (the major motivator for adding it at all was I think for strict CSP), and our documentation said setting the value to zero would do that. However, it did the opposite: url-loader treated zero as "no limit".

The update to 2.x fixes this; zero means nothing gets inlined. The other changes from the version bump shouldn't affect us:
- minimum node version is 8.9.x, we already require 8.10.x
- the limit was "greater than", is now "greater than or equal to"
* Add question issue template

* Fix bug report template formatting

* Fix bug report template formatting

* Add labels to pull request template
* Update deploy instructions in contributing guide

* Update docs publishing instructions
@dmile dmile closed this Jul 28, 2019
@dmile dmile deleted the fix-hmr-for-firefox branch July 28, 2019 14:59
@dmile
Copy link
Contributor Author

dmile commented Jul 28, 2019

the CI has a lot of failures here.

@mrmckeb The same PR with CI updates: #7444

@lock lock bot locked and limited conversation to collaborators Aug 2, 2019
@ianschmitz ianschmitz removed this from the 3.1 milestone Aug 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.