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

Justin808/updates for hmr with webpacker v4 #1240

Merged
merged 6 commits into from
May 23, 2020

Conversation

justin808
Copy link
Member

@justin808 justin808 commented Jan 9, 2020

This change is Reviewable

@justin808 justin808 force-pushed the justin808/updates-for-hmr-with-webpacker-v4 branch from 8106929 to e76e0e8 Compare January 9, 2020 08:21
@justin808 justin808 force-pushed the justin808/updates-for-hmr-with-webpacker-v4 branch 2 times, most recently from 58daa51 to ae55cba Compare March 9, 2020 02:39
@justin808 justin808 force-pushed the justin808/updates-for-hmr-with-webpacker-v4 branch from ae55cba to abf6856 Compare May 6, 2020 09:45
@justin808 justin808 force-pushed the justin808/updates-for-hmr-with-webpacker-v4 branch from abf6856 to 5a68024 Compare May 15, 2020 02:26
Added configuration option `same_bundle_for_client_and_server` with default `false` because

1. Production applications would typically have a server bundle that differs from the client bundle
2. This change only affects trying to use HMR with react_on_rails with rails/webpacker.

The previous behavior was to always go to the webpack-dev-server for the server bundle if the
webpack-dev-server was running _and_ the server bundle was found in the `manifest.json`.

If you are using the **same bundle for client and server rendering**, then set this configuration option
to `true`.

Also, remove requirement that server bundle not have the default deployment
path. A subdirectory can be specified for the server_bundle_js_file.
@justin808 justin808 force-pushed the justin808/updates-for-hmr-with-webpacker-v4 branch from 5a68024 to c934d55 Compare May 18, 2020 09:19
@justin808 justin808 requested review from Judahmeek and ashgaliyev May 19, 2020 05:53
Copy link
Contributor

@ashgaliyev ashgaliyev left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewed 20 of 20 files at r1.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @Judahmeek)

@justin808 justin808 merged commit 6e6367b into master May 23, 2020
@justin808 justin808 deleted the justin808/updates-for-hmr-with-webpacker-v4 branch May 23, 2020 23:34
justin808 added a commit that referenced this pull request Jun 9, 2020
* Added same_bundle_for_client_and_server

Added configuration option `same_bundle_for_client_and_server` with default `false` because

1. Production applications would typically have a server bundle that differs from the client bundle
2. This change only affects trying to use HMR with react_on_rails with rails/webpacker.

The previous behavior was to always go to the webpack-dev-server for the server bundle if the
webpack-dev-server was running _and_ the server bundle was found in the `manifest.json`.

If you are using the **same bundle for client and server rendering**, then set this configuration option
to `true`.

Also, remove the requirement that the server bundle have the default deployment
path. A subdirectory can be specified for the server_bundle_js_file.
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.

2 participants