use https://melange.re/v4.0.0

davesnx · davesnx · commit b9a13f042d52 · 2025-02-26T13:29:32.000+01:00
diff --git a/docs/element-type-is-invalid.md b/docs/element-type-is-invalid.md
@@ -12,7 +12,7 @@ This likely means that:
 - The JS component uses ES6 default export (`export default MyComponent`) (or, you forgot to export the component altogether!).
 - You're using Babel/Webpack to compile those ES6 modules.
 
-This is a common mistake. Please see Melange's [Import an ES6 Default Value](https://melange.re/v2.0.0/communicate-with-javascript/#default-es6-values). Aka, instead of:
+This is a common mistake. Please see Melange's [Import an ES6 Default Value](https://melange.re/v4.0.0/communicate-with-javascript/#default-es6-values). Aka, instead of:
 
 ```reason
 [@mel.module] external myJSReactClass: ReasonReact.reactClass = "./myJSReactClass";
diff --git a/docs/event.md b/docs/event.md
@@ -8,7 +8,7 @@ React.Event module contains all event types as submodules, e.g. `React.Event.For
 
 You can access their properties using the `React.Event.{{EventName}}.{{property}}` method. For example, to access the `target` property of a `React.Event.Form.t` event, you would use `React.Event.Form.target`.
 
-Since `target` is a JavaScript Object, those are typed as [`Js.t`](https://melange.re/v2.0.0/communicate-with-javascript/#using-jst-objects). If you're accessing fields on an object, like `event.target.value`, you'd use [Melange's `##` object access FFI](https://melange.re/v2.0.0/communicate-with-javascript/#using-jst-objects):
+Since `target` is a JavaScript Object, those are typed as [`Js.t`](https://melange.re/v4.0.0/communicate-with-javascript/#using-jst-objects). If you're accessing fields on an object, like `event.target.value`, you'd use [Melange's `##` object access FFI](https://melange.re/v4.0.0/communicate-with-javascript/#using-jst-objects):
 
 ```reason
 React.Event.Form.target(event)##value;
diff --git a/docs/installation.md b/docs/installation.md
@@ -6,7 +6,7 @@ ReasonReact is built to work with [Melange](https://melange.re/) and [Reason](ht
 
 If you want to build a new app or a new website with ReasonReact and Melange, we recommend to use a package manager such as [opam](https://opam.ocaml.org/) to download and install the required dependencies.
 
-There are other alternatives available, such as [esy](https://esy.sh/) or [nix](https://nixos.org/). See [Melange documentation](https://melange.re/v2.0.0/getting-started/#alternative-package-managers-experimental) for details.
+There are other alternatives available, such as [esy](https://esy.sh/) or [nix](https://nixos.org/). See [Melange documentation](https://melange.re/v4.0.0/getting-started/#alternative-package-managers-experimental) for details.
 
 #### Requirements
 
@@ -17,11 +17,11 @@ There are other alternatives available, such as [esy](https://esy.sh/) or [nix](
 
 Melange is the toolchain that compiles Reason and OCaml to JavaScript. It integrates with dune to provide a seamless experience for building and running your project.
 
-Follow the getting started guide on [Melange's documentation](https://melange.re/v2.0.0/getting-started/) to continue.
+Follow the getting started guide on [Melange's documentation](https://melange.re/v4.0.0/getting-started/) to continue.
 
 ## Editor Setup
 
-Since Reason is an alternative syntax for OCaml, we integrate seamlessly into the official OCaml editor toolchain. Following the recommendation from [Melange's documentation](https://melange.re/v2.0.0/getting-started/#editor-integration).
+Since Reason is an alternative syntax for OCaml, we integrate seamlessly into the official OCaml editor toolchain. Following the recommendation from [Melange's documentation](https://melange.re/v4.0.0/getting-started/#editor-integration).
 
 - For VSCode, we recommend using the [vscode-ocaml-platform](https://github.com/ocamllabs/vscode-ocaml-platform) plugin
 - For other editors (Emacs and Vim), we recommend using a language server client plugin of your choice, and pairing it with [ocaml-lsp](https://github.com/ocaml/ocaml-lsp).
diff --git a/docs/intro-example.md b/docs/intro-example.md
@@ -37,7 +37,7 @@ if (root != null) {
 
 ### Using Greeting in an existing JavaScript/Typescript application
 
-It's easy to import a ReasonReact component into your existing app. After being transpiled to JS, all Reason components will have `.js` as extension by default and export a function component called `make`. You can change it with [module_systems](https://melange.re/v2.0.0/build-system/#commonjs-or-es6-modules) field inside a [`melange.emit` stanza](https://dune.readthedocs.io/en/stable/melange.html#melange-emit).
+It's easy to import a ReasonReact component into your existing app. After being transpiled to JS, all Reason components will have `.js` as extension by default and export a function component called `make`. You can change it with [module_systems](https://melange.re/v4.0.0/build-system/#commonjs-or-es6-modules) field inside a [`melange.emit` stanza](https://dune.readthedocs.io/en/stable/melange.html#melange-emit).
 
 ```js
 /* file: App.js */
diff --git a/website/blog/2023-06-11-reborn.md b/website/blog/2023-06-11-reborn.md
@@ -8,13 +8,13 @@ Today, we are happy to announce that ReasonReact is back and will be maintained
 
 ## What's changing?
 
-We released ReasonReact to the [opam repository](https://ocaml.org/p/reason-react/latest). In the Melange docs, we document [how to depend](https://melange.re/v2.0.0/package-management/) on packages in opam.
+We released ReasonReact to the [opam repository](https://ocaml.org/p/reason-react/latest). In the Melange docs, we document [how to depend](https://melange.re/v4.0.0/package-management/) on packages in opam.
 
 We updated the documentation to reflect these new changes and we will continue to improve it over time.
 
 ## Adopting ReasonReact
 
-To use ReasonReact, you must be using Melange. [Get started here](https://melange.re/v2.0.0/getting-started/).
+To use ReasonReact, you must be using Melange. [Get started here](https://melange.re/v4.0.0/getting-started/).
 
 Next:
 
diff --git a/website/blog/2023-09-13-reason-react-ppx.md b/website/blog/2023-09-13-reason-react-ppx.md
@@ -27,7 +27,7 @@ Take a look at [reasonml/reason-react/releases/tag/0.12.0](https://github.com/re
 
 ## Updating to latest
 
-ReasonReact works best with Melange. [Get started here](https://melange.re/v2.0.0/getting-started/).
+ReasonReact works best with Melange. [Get started here](https://melange.re/v4.0.0/getting-started/).
 
 Next:
 
@@ -42,7 +42,7 @@ Next:
 
 - Remove any usage of `ReactDOM.props`
 - Bump React.js version to v17/v18 to use the new JSX transformation
-- We added `depexts` in opam for `react` and `react-dom` to ensure you have the correct versions installed from npm. [`depexts`](https://opam.ocaml.org/packages/opam-depext/) is the mechanism by opam to ensure the correct versions of external dependencies are present in your system. Learn more here on the Melange documentation page about [bindings and package management](https://melange.re/v2.0.0/package-management/#bindings-and-package-management):
+- We added `depexts` in opam for `react` and `react-dom` to ensure you have the correct versions installed from npm. [`depexts`](https://opam.ocaml.org/packages/opam-depext/) is the mechanism by opam to ensure the correct versions of external dependencies are present in your system. Learn more here on the Melange documentation page about [bindings and package management](https://melange.re/v4.0.0/package-management/#bindings-and-package-management):
 
   ```clojure
     depexts: [
