You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/upgrade-guide/index.md
+32Lines changed: 32 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,6 +48,38 @@ You should take the following actions for your Volto 19 projects.
48
48
49
49
If you can't upgrade immediately, you may continue to run Volto 19 on Node.js 20 at your own risk, but be aware that issues specific to Node.js 20 will not be fixed in the Volto core CI or releases.
50
50
51
+
(replace-razzle-with-volto-razzle)=
52
+
53
+
### Replace `razzle` with `@volto/razzle` (fork)
54
+
```{versionchanged} Volto 19.0.0-alpha.14
55
+
```
56
+
57
+
`@volto/razzle` is a fork of the upstream `razzle` package that contains Volto-specific fixes and patches.
58
+
Use `@volto/razzle` in your Volto 19 projects when either you need the Volto-compatible build behavior, or the Volto team provides temporary patches that are not yet merged upstream in Razzle.
59
+
60
+
For most projects, no action is required.
61
+
The fork maintains full compatibility with the original `razzle` package, preserving all CLI entry points such as `razzle start`, `razzle build`, and `razzle test`.
62
+
63
+
However, if you have customized Volto's internals in your project—for example, by importing internal modules directly from the `razzle` package such as `require('razzle/some/path')`—then you need to update those imports to reference `@volto/razzle` instead.
64
+
65
+
To verify whether your project requires updates, search for any direct references to internal `razzle` modules:
0 commit comments