react-hot-loader - npm Package Compare versions

Comparing version 4.12.18 to 4.12.19

CHANGELOG.md

		@@ -5,2 +5,9 @@ # Changelog

		### [4.12.19](https://github.com/gaearon/react-hot-loader/compare/v4.12.18...v4.12.19) (2020-01-22)


		### Bug Fixes

		* don't record signatures of local hooks, fixes [#1412](https://github.com/gaearon/react-hot-loader/issues/1412) ([#1413](https://github.com/gaearon/react-hot-loader/issues/1413)) ([c159844](https://github.com/gaearon/react-hot-loader/commit/c159844))

		### [4.12.18](https://github.com/gaearon/react-hot-loader/compare/v4.12.17...v4.12.18) (2019-11-16)
		@@ -7,0 +14,0 @@

dist/babel.development.js

		@@ -220,2 +220,4 @@ 'use strict';
		return !isBuiltinHook(call.name);
		}).filter(function (call) {
		return scope.parent.hasBinding(call.name);
		}).map(function (call) {
		@@ -222,0 +224,0 @@ return t.cloneDeep(call.callee);

package.json

		{
		"name": "react-hot-loader",
		"version": "4.12.18",
		"version": "4.12.19",
		"description": "Tweak React components in real time.",
		@@ -5,0 +5,0 @@ "main": "index.js",

README.md

		@@ -19,2 +19,13 @@ # React Hot Loader

		# Deprecation note

		React-Hot-Loader was your friendly neightbour, living outside of React. But it was limiting it's powers and causing not the greatest experience. It's time to make a next step.

		React-Hot-Loader is expected to be replaced by [React Fast Refresh](https://github.com/facebook/react/issues/16604). Please remove React-Hot-Loader if Fast Refresh is currently supported on your environment.

		* `React Native` - [supports Fast Refresh](https://facebook.github.io/react-native/docs/fast-refresh) since 0.61.
		* `parcel 2` - [supports Fast Refresh](https://github.com/facebook/react/issues/16604#issuecomment-556082893) since alpha 3.
		* `webpack` - no support yet, use React-Hot-Loader
		* `other bundler` - no support yet, use React-Hot-Loader

		## Install
		@@ -155,2 +166,16 @@

		## What about production?

		The webpack patch, `hot`, Babel plugin, `@hot-loader/react-dom` etc. are all safe to use in production; they leave a minimal footprint, so there is no need to complicate your configuration based on the environment. Using the Babel plugin in production is even recommended because it switches to cleanup mode.

		Just ensure that the production mode has been properly set, both as an environment variable and in your bundler. E.g. with webpack you would build your code by running something like:

		```
		NODE_ENV=production webpack --mode production
		```

		`NODE_ENV=production` is needed for the Babel plugin, while `--mode production` uses [`webpack.DefinePlugin`](https://webpack.js.org/plugins/define-plugin/) to set `process.env.NODE_ENV` inside the compiled code itself, which is used by `hot` and `@hot-loader/react-dom`.

		Make sure to watch your bundle size when implementing react-hot-loader to ensure that you did it correctly.

		## Limitations
		@@ -401,3 +426,3 @@

		If you use a not-yet-friendly library, like [react-async-component](github.com/ctrlplusb/react-async-component),
		If you use a not-yet-friendly library, like [react-async-component](https://github.com/ctrlplusb/react-async-component),
		or are having problems with hot reloading failing to reload code-split components,
		@@ -433,3 +458,5 @@ you can manually mark the components below the code-split boundaries.
		### Out-of-bound warning

		You may see the following warning when code-split components are updated:

		```console
		@@ -436,0 +463,0 @@ React-Hot-Loader: some components were updated out-of-bound. Updating your app to reconcile the changes.

react-hot-loader - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics