@lynx-js/react-refresh-webpack-plugin-canary 0.4.5 → 0.4.6-canary-20261027-749147c8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +10 -0
- package/README.md +33 -0
- package/package.json +3 -3
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,15 @@
|
|
|
1
1
|
# @lynx-js/react-refresh-webpack-plugin
|
|
2
2
|
|
|
3
|
+
## 0.4.6-canary-20261027063858-749147c82c3e0bb06f1e92567a5afec909baf19b
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- Apply main-thread hot updates to loaded async chunks, keep async definition modules stable when worklets are added or removed, and retain background HMR on hosts without Native bundle loading. Centralize the shared HMR runtime identifiers. ([#4179](https://github.com/lynx-family/lynx-stack/pull/4179))
|
|
8
|
+
|
|
9
|
+
Keep the refresh plugin compatible with the planned `react-webpack-plugin` 0.15 release while preserving its existing peer dependency ranges.
|
|
10
|
+
- Updated dependencies [[`7d498ae`](https://github.com/lynx-family/lynx-stack/commit/7d498aece52a20e77abc19e2a4579333861c11da), [`7d498ae`](https://github.com/lynx-family/lynx-stack/commit/7d498aece52a20e77abc19e2a4579333861c11da)]:
|
|
11
|
+
- @lynx-js/react-webpack-plugin@0.15.0-canary-20261027063858-749147c82c3e0bb06f1e92567a5afec909baf19b
|
|
12
|
+
|
|
3
13
|
## 0.4.5
|
|
4
14
|
|
|
5
15
|
### Patch Changes
|
package/README.md
CHANGED
|
@@ -1,3 +1,36 @@
|
|
|
1
1
|
<h2 align="center">@lynx-js/react-refresh-webpack-plugin</h2>
|
|
2
2
|
|
|
3
3
|
A webpack plugin to hot refresh for Lynx
|
|
4
|
+
|
|
5
|
+
## Main Thread Functions
|
|
6
|
+
|
|
7
|
+
Rspeedy's ReactLynx HMR integration updates Main Thread Functions and their
|
|
8
|
+
shared dependencies before refreshing the corresponding background components.
|
|
9
|
+
This also refreshes existing event bindings when a dependency changes without
|
|
10
|
+
changing the function's worklet ID. No additional application API is required.
|
|
11
|
+
Application updates include already loaded async chunks and the first worklet
|
|
12
|
+
added to a background-only module within an async scope.
|
|
13
|
+
|
|
14
|
+
Each thread loads its own versioned update bundle through Native `fetchBundle`
|
|
15
|
+
and `loadScript`. The shared HMR loader reads a manifest section and the sections
|
|
16
|
+
for the requested update chunks. Background sections retain the existing SDK
|
|
17
|
+
runtime wrapper and app scope; normal lazy loading keeps its existing loader.
|
|
18
|
+
Background bundles do not carry worklet implementations for cross-thread HMR;
|
|
19
|
+
the compiler supplies their definitions to the main-thread bundle.
|
|
20
|
+
A failed update on either thread, or a missing main-thread
|
|
21
|
+
completion, triggers a full page reload. Coordinated updates allow up to ten
|
|
22
|
+
seconds for main-thread completion, then up to ten seconds for background
|
|
23
|
+
application. Pending updates from the old page are discarded. Compatible component updates preserve `useState`; memoized values,
|
|
24
|
+
including `useMainThreadRef`, follow the existing Fast Refresh reset behavior.
|
|
25
|
+
|
|
26
|
+
This integration applies to application HMR and uses the host's existing Native
|
|
27
|
+
loading and DevTool reload capabilities. It does not add standalone lazy-bundle
|
|
28
|
+
HMR or change production bundles.
|
|
29
|
+
|
|
30
|
+
If the host lacks main-thread `fetchBundle` or `loadScript`, the coordinator
|
|
31
|
+
disables main-thread updates and retains the existing background HMR path.
|
|
32
|
+
Background Native loading also requires the SDK to initialize the app wrapper:
|
|
33
|
+
hosts without these APIs or that initialization capability retain the original
|
|
34
|
+
background loader. The manifest probes initialization before update code runs.
|
|
35
|
+
Actual Native load or application failures still trigger a reload. These
|
|
36
|
+
fallbacks do not add Main Thread Function HMR to hosts without main-thread loading.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lynx-js/react-refresh-webpack-plugin-canary",
|
|
3
|
-
"version": "0.4.
|
|
3
|
+
"version": "0.4.6-canary-20261027-749147c8",
|
|
4
4
|
"description": "A webpack plugin to hot refresh for Lynx.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"webpack",
|
|
@@ -34,9 +34,9 @@
|
|
|
34
34
|
"README.md"
|
|
35
35
|
],
|
|
36
36
|
"devDependencies": {
|
|
37
|
-
"@lynx-js/react": "npm:@lynx-js/react-canary@0.129.
|
|
37
|
+
"@lynx-js/react": "npm:@lynx-js/react-canary@0.129.1-canary-20261027-749147c8",
|
|
38
38
|
"@lynx-js/react-refresh": "0.1.0",
|
|
39
|
-
"@lynx-js/react-webpack-plugin": "npm:@lynx-js/react-webpack-plugin-canary@0.
|
|
39
|
+
"@lynx-js/react-webpack-plugin": "npm:@lynx-js/react-webpack-plugin-canary@0.15.0-canary-20261027-749147c8",
|
|
40
40
|
"@lynx-js/test-tools": "0.0.0",
|
|
41
41
|
"@microsoft/api-extractor": "7.59.4",
|
|
42
42
|
"@rspack/core": "2.2.7",
|