remove .mdx extensions from mdx file links

jderochervlk · jderochervlk · commit c2709ac9c891 · 2025-11-13T13:31:12.000-05:00
diff --git a/markdown-pages/blogposts/2022-08-25-release-10-0-0.mdx b/markdown-pages/blogposts/2022-08-25-release-10-0-0.mdx
@@ -14,7 +14,7 @@ ReScript version 10 is available! Version 10 is a culmination of over a year's w
 npm install rescript@10
 ```
 
-All changes are listed [here](https://github.com/rescript-lang/rescript/blob/10.0_release/CHANGELOG.md). Let's take a tour of a few of the features we're extra excited about.
+All changes are listed [here](https://github.com/rescript-lang/rescript/blob/10.0_release/CHANGELOG). Let's take a tour of a few of the features we're extra excited about.
 
 ## Faster builds with native M1 support
 
@@ -86,7 +86,7 @@ Version 10 brings the building blocks needed for a number of exciting new featur
 
 ## Upgrade guide
 
-Please see the detailed [changelog](https://github.com/rescript-lang/rescript/blob/10.0_release/CHANGELOG.md) for a list of breaking changes.
+Please see the detailed [changelog](https://github.com/rescript-lang/rescript/blob/10.0_release/CHANGELOG) for a list of breaking changes.
 Each breaking change lists suggestions on how to upgrade your project.
 This can be out of your control in case of dependencies. In that case, please raise issues with the maintainers of those libraries.
 
diff --git a/markdown-pages/blogposts/2023-02-02-release-10-1.mdx b/markdown-pages/blogposts/2023-02-02-release-10-1.mdx
@@ -283,7 +283,7 @@ export {
 
 We provide a full [migration guide](/docs/react/latest/migrate-react) with all the details of an migration.
 
-Make sure to also check out the [rescript-react changelog](https://github.com/rescript-lang/rescript-react/blob/master/CHANGELOG.md) as well.
+Make sure to also check out the [rescript-react changelog](https://github.com/rescript-lang/rescript-react/blob/master/CHANGELOG) as well.
 
 ## What's next?
 
diff --git a/markdown-pages/blogposts/2024-01-11-release-11-0-0.mdx b/markdown-pages/blogposts/2024-01-11-release-11-0-0.mdx
@@ -18,7 +18,7 @@ npm install rescript@11
 
 To upgrade your project or to find out if there are any breaking changes that affect you, please follow the [migration guide](/docs/manual/migrate-to-v11).
 
-The complete list of changes can be found [here](https://github.com/rescript-lang/rescript/blob/v11.0.0/CHANGELOG.md). Let's have a look at the most notable improvements.
+The complete list of changes can be found [here](https://github.com/rescript-lang/rescript/blob/v11.0.0/CHANGELOG). Let's have a look at the most notable improvements.
 
 ## Highlights
 
diff --git a/markdown-pages/blogposts/archived/2019-11-18-whats-new-in-7-pt1.mdx b/markdown-pages/blogposts/archived/2019-11-18-whats-new-in-7-pt1.mdx
@@ -17,7 +17,7 @@ since this release we are moving forward and focusing on release 7.\* (for OCaml
 4.06).
 
 This is a major release comes with lots of nice features listed
-[here](https://github.com/BuckleScript/bucklescript/blob/master/Changes.md).
+[here](https://github.com/BuckleScript/bucklescript/blob/master/Changes).
 
 We talk about some highlights here
 
diff --git a/markdown-pages/blogposts/archived/2020-08-03-bucklescript-release-8-2.mdx b/markdown-pages/blogposts/archived/2020-08-03-bucklescript-release-8-2.mdx
@@ -16,6 +16,6 @@ Besides the exciting string literal types, this release continues to deliver bet
 
 Thanks to the integration of Flow parser, we are able to make the JS interop [more safe and expressive](https://github.com/BuckleScript/bucklescript/issues/4463)
 
-The full changes are listed [here](https://github.com/BuckleScript/bucklescript/blob/master/Changes.md)
+The full changes are listed [here](https://github.com/BuckleScript/bucklescript/blob/master/Changes)
 
 Enjoy!
diff --git a/markdown-pages/docs/manual/array-and-list.mdx b/markdown-pages/docs/manual/array-and-list.mdx
@@ -192,7 +192,7 @@ var anotherList = {
 
 #### Access
 
-`switch` (described in the [pattern matching section](pattern-matching-destructuring.md)) is usually used to access list items:
+`switch` (described in the [pattern matching section](pattern-matching-destructuring)) is usually used to access list items:
 
 <CodeTab labels={["ReScript", "JS Output"]}>
 
diff --git a/markdown-pages/docs/manual/bind-to-js-function.mdx b/markdown-pages/docs/manual/bind-to-js-function.mdx
@@ -109,7 +109,7 @@ In a `send`, the object is always the first argument. Actual arguments of the me
 
 ### Chaining
 
-Ever used `foo().bar().baz()` chaining ("fluent api") in JS OOP? We can model that in ReScript too, through the [pipe operator](pipe.md).
+Ever used `foo().bar().baz()` chaining ("fluent api") in JS OOP? We can model that in ReScript too, through the [pipe operator](pipe).
 
 ### Nested function call
 
@@ -164,7 +164,7 @@ var v = Path.join("a", "b");
 
 </CodeTab>
 
-`module` will be explained in [Import from/Export to JS](import-from-export-to-js.md).
+`module` will be explained in [Import from/Export to JS](import-from-export-to-js).
 
 ## Modeling Polymorphic Function
 
diff --git a/markdown-pages/docs/manual/bind-to-js-object.mdx b/markdown-pages/docs/manual/bind-to-js-object.mdx
@@ -15,7 +15,7 @@ JavaScript objects are a combination of several use-cases:
 - As a class.
 - As a module to import/export.
 
-ReScript cleanly separates the binding methods for JS object based on these 4 use-cases. This page documents the first three. Binding to JS module objects is described in the [Import from/Export to JS](import-from-export-to-js.md) section.
+ReScript cleanly separates the binding methods for JS object based on these 4 use-cases. This page documents the first three. Binding to JS module objects is described in the [Import from/Export to JS](import-from-export-to-js) section.
 
 {/* TODO: mention scope here too? */}
 
@@ -47,7 +47,7 @@ var johnName = MySchool.john.name;
 
 </CodeTab>
 
-External is documented [here](external.md). `@module` is documented [here](import-from-export-to-js.md).
+External is documented [here](external). `@module` is documented [here](import-from-export-to-js).
 
 If you want or need to use different field names on the ReScript and the JavaScript side, you can use the `@as` decorator:
 
@@ -92,7 +92,7 @@ var value = [7, "baz"];
 
 ### Bind Using ReScript Object
 
-Alternatively, you can use [ReScript object](object.md) to model a JS object too:
+Alternatively, you can use [ReScript object](object) to model a JS object too:
 
 <CodeTab labels={["ReScript", "JS Output"]}>
 
diff --git a/markdown-pages/docs/manual/control-flow.mdx b/markdown-pages/docs/manual/control-flow.mdx
@@ -10,7 +10,7 @@ order: 14
 
 ReScript supports `if`, `else`, ternary expression (`a ? b : c`), `for` and `while`.
 
-ReScript also supports our famous pattern matching, which will be covered in [its own section](pattern-matching-destructuring.md)
+ReScript also supports our famous pattern matching, which will be covered in [its own section](pattern-matching-destructuring)
 
 ## If-Else & Ternary
 
@@ -94,7 +94,7 @@ var message = isMorning ? "Good morning!" : "Hello!";
 
 </CodeTab>
 
-**`if-else` and ternary are much less used** in ReScript than in other languages; [Pattern-matching](pattern-matching-destructuring.md) kills a whole category of code that previously required conditionals.
+**`if-else` and ternary are much less used** in ReScript than in other languages; [Pattern-matching](pattern-matching-destructuring) kills a whole category of code that previously required conditionals.
 
 ## For Loops
 
@@ -190,7 +190,7 @@ while (testCondition) {
 
 ### Tips & Tricks
 
-There's no loop-breaking `break` keyword (nor early `return` from functions, for that matter) in ReScript. However, we can break out of a while loop easily through using a [mutable binding](mutation.md).
+There's no loop-breaking `break` keyword (nor early `return` from functions, for that matter) in ReScript. However, we can break out of a while loop easily through using a [mutable binding](mutation).
 
 <CodeTab labels={["ReScript", "JS Output"]}>
 
diff --git a/markdown-pages/docs/manual/converting-from-js.mdx b/markdown-pages/docs/manual/converting-from-js.mdx
@@ -308,7 +308,7 @@ The moment you produce extra conversion code in the output, your skeptical teamm
 - Paste the JS code into a new ReScript file as embedded raw JS code.
 - Compile and keep the output file open. Check and diff against original JS file. Free regression tests.
 - Always make sure your file is syntactically valid. Don't worry about fixing types before that.
-- (Ab)use [object](object.md) accesses to quickly convert things over.
+- (Ab)use [object](object) accesses to quickly convert things over.
 - Optionally clean up the types for robustness.
 - Don't go overboard and turn off your boss and fellow teammates.
 - Proudly display that you've conserved the semantics and performance characteristics during the conversion by showing your teammates the eerily familiar output.
diff --git a/markdown-pages/docs/manual/editor-plugins.mdx b/markdown-pages/docs/manual/editor-plugins.mdx
@@ -153,7 +153,7 @@ Below is a list of all the scenarios where using dots trigger completion in addi
 
 #### Objects
 
-When writing a `.` on something that's a [structural object](object.md), you'll get completions for those object properties. Example:
+When writing a `.` on something that's a [structural object](object), you'll get completions for those object properties. Example:
 
 ```res
 let obj = {
diff --git a/markdown-pages/docs/manual/embed-raw-javascript.mdx b/markdown-pages/docs/manual/embed-raw-javascript.mdx
@@ -113,4 +113,4 @@ Embedding raw JS snippets isn't the best way to experience ReScript, though it's
 
 At the end, we get a fully safe, converted ReScript file whose JS output is clean enough that we can confidently assert that no new bug has been introduced during the conversion process.
 
-We have a small guide on this iteration [here](converting-from-js.md). Feel free to peruse it later.
+We have a small guide on this iteration [here](converting-from-js). Feel free to peruse it later.
diff --git a/markdown-pages/docs/manual/exception.mdx b/markdown-pages/docs/manual/exception.mdx
@@ -8,7 +8,7 @@ order: 19
 
 # Exception
 
-Exceptions are just a special kind of variant, thrown in **exceptional** cases (don't abuse them!). Consider using the [`option`](null-undefined-option.mdx) or [`result`](api/core/result) type for recoverable errors.
+Exceptions are just a special kind of variant, thrown in **exceptional** cases (don't abuse them!). Consider using the [`option`](null-undefined-option) or [`result`](api/core/result) type for recoverable errors.
 
 You can create your own exceptions like you'd make a variant (exceptions need to be capitalized too).
 
diff --git a/markdown-pages/docs/manual/external.mdx b/markdown-pages/docs/manual/external.mdx
@@ -28,7 +28,7 @@ order: 3
 
 </CodeTab>
 
-There are several kinds of `external`s, differentiated and/or augmented through the [attribute](attribute.md) they carry. This page deals with the general, shared mechanism behind most `external`s. The different `external`s are documented in their respective pages later. A few notable ones:
+There are several kinds of `external`s, differentiated and/or augmented through the [attribute](attribute) they carry. This page deals with the general, shared mechanism behind most `external`s. The different `external`s are documented in their respective pages later. A few notable ones:
 
 - `@val`, `@scope`: [bind to global JS values](bind-to-global-js-values).
 - `@module`: [bind to JS imported/exported values](import-from-export-to-js).
diff --git a/markdown-pages/docs/manual/function.mdx b/markdown-pages/docs/manual/function.mdx
@@ -217,7 +217,7 @@ function drawCircle(color, radius) {
 
 When given in this syntax, `radius` is **wrapped** in the standard library's `option` type, defaulting to `None`. If provided, it'll be wrapped with a `Some`. So `radius`'s type value is `None | Some(int)` here.
 
-More on `option` type [here](null-undefined-option.md).
+More on `option` type [here](null-undefined-option).
 
 ### Signatures and Type Annotations
 
diff --git a/markdown-pages/docs/manual/import-export.mdx b/markdown-pages/docs/manual/import-export.mdx
@@ -38,4 +38,4 @@ To only export a few selected things, use a `.resi` [interface file](module.md#s
 
 ## Work with JavaScript Import & Export
 
-To see how to import JS modules and export stuff for JS consumption, see the JavaScript Interop section's [Import from/Export to JS](import-from-export-to-js.md).
+To see how to import JS modules and export stuff for JS consumption, see the JavaScript Interop section's [Import from/Export to JS](import-from-export-to-js).
diff --git a/markdown-pages/docs/manual/import-from-export-to-js.mdx b/markdown-pages/docs/manual/import-from-export-to-js.mdx
@@ -8,9 +8,9 @@ order: 7
 
 # Import from/Export to JS
 
-You've seen how ReScript's idiomatic [Import & Export](import-export.md) works. This section describes how we work with importing stuff from JavaScript and exporting stuff for JavaScript consumption.
+You've seen how ReScript's idiomatic [Import & Export](import-export) works. This section describes how we work with importing stuff from JavaScript and exporting stuff for JavaScript consumption.
 
-If you're looking for react-specific interop guidance, check out the [React JS Interop guide](../../react/latest/import-export-reactjs.mdx).
+If you're looking for react-specific interop guidance, check out the [React JS Interop guide](../../react/latest/import-export-reactjs).
 
 **Note**: due to JS ecosystem's module compatibility issues, our advice of keeping your ReScript file's compiled JS output open in a tab applies here **more than ever**, as you don't want to subtly output the wrong JS module import/export code, on top of having to deal with Babel/Webpack/Jest/Node's CommonJS \<-> JavaScript module compatibility shims.
 
@@ -29,7 +29,7 @@ The format is [configurable in via `rescript.json`](build-configuration.md#packa
 
 ### Import a JavaScript Module's Named Export
 
-Use the `module` [external](external.md):
+Use the `module` [external](external):
 
 <CodeTab labels={["ReScript", "JS Output (Module)", "JS Output (CommonJS)"]}>
 
@@ -209,7 +209,7 @@ async function main() {
 
 ### Export a Named Value
 
-As mentioned in ReScript's idiomatic [Import & Export](import-export.md), every let binding and module is exported by default to other ReScript modules (unless you use a `.resi` [interface file](module#signatures)). If you open up the compiled JS file, you'll see that these values can also directly be used by a _JavaScript_ file too.
+As mentioned in ReScript's idiomatic [Import & Export](import-export), every let binding and module is exported by default to other ReScript modules (unless you use a `.resi` [interface file](module#signatures)). If you open up the compiled JS file, you'll see that these values can also directly be used by a _JavaScript_ file too.
 
 ### Export a `default` Value
 
diff --git a/markdown-pages/docs/manual/interop-cheatsheet.mdx b/markdown-pages/docs/manual/interop-cheatsheet.mdx
@@ -264,7 +264,7 @@ padLeft("Hello World", "Message from ReScript: ");
 
 ## JS Module Interop
 
-[See here](import-from-export-to-js.md)
+[See here](import-from-export-to-js)
 
 ## Dangerous Type Cast
 
diff --git a/markdown-pages/docs/manual/interop-with-js-build-systems.mdx b/markdown-pages/docs/manual/interop-with-js-build-systems.mdx
@@ -48,7 +48,7 @@ This will:
 
 "What if my build system uses a CSS/png/whatever loader and I'd like to use it in ReScript?"
 
-Loaders are indeed troublesome; in the meantime, please use e.g. `%raw("require('./myStyles.css')")` at the top of your file. This just uses [`raw`](embed-raw-javascript.md) to compile the snippet into an actual JS require.
+Loaders are indeed troublesome; in the meantime, please use e.g. `%raw("require('./myStyles.css')")` at the top of your file. This just uses [`raw`](embed-raw-javascript) to compile the snippet into an actual JS require.
 
 ## Getting Project's Dependencies
 
diff --git a/markdown-pages/docs/manual/lazy-values.mdx b/markdown-pages/docs/manual/lazy-values.mdx
@@ -35,7 +35,7 @@ let expensiveFilesRead = Lazy.make(() => {
 
 </CodeTab>
 
-**Note**: a lazy value is **not** a [shared data type](shared-data-types.md). Don't rely on its runtime representation in your JavaScript code.
+**Note**: a lazy value is **not** a [shared data type](shared-data-types). Don't rely on its runtime representation in your JavaScript code.
 
 ## Execute The Lazy Computation
 
diff --git a/markdown-pages/docs/manual/let-binding.mdx b/markdown-pages/docs/manual/let-binding.mdx
@@ -152,7 +152,7 @@ console.log(1);
 </CodeTab>
 
 The binding you refer to is whatever's the closest upward. No mutation here!
-If you need _real_ mutation, e.g. passing a value around, have it modified by many pieces of code, we provide a slightly heavier [mutation feature](mutation.md).
+If you need _real_ mutation, e.g. passing a value around, have it modified by many pieces of code, we provide a slightly heavier [mutation feature](mutation).
 
 ## Private let bindings
 
diff --git a/markdown-pages/docs/manual/libraries.mdx b/markdown-pages/docs/manual/libraries.mdx
@@ -24,6 +24,6 @@ Search `rescript`-related packages on NPM, or use our [Package Index](/packages)
 
 If you can't find what you're looking for, remember that **you don't need a wrapper** to use a JS library:
 
-- Most JS data types, such as array and objects, [map over cleanly to ReScript and vice-versa](shared-data-types.md).
+- Most JS data types, such as array and objects, [map over cleanly to ReScript and vice-versa](shared-data-types).
 - You also have access to the familiar [Core API](api/core).
 - You can use a JavaScript library without needing to install dedicated binding libraries. Check the [`external`](external) page.
diff --git a/markdown-pages/docs/manual/null-undefined-option.mdx b/markdown-pages/docs/manual/null-undefined-option.mdx
@@ -28,7 +28,7 @@ type option<'a> = None | Some('a)
 
 It means "a value of type option is either None (representing nothing) or that actual value wrapped in a Some".
 
-**Note** how the `option` type is just a regular [variant](variant.md).
+**Note** how the `option` type is just a regular [variant](variant).
 
 ## Example
 
@@ -65,7 +65,7 @@ var licenseNumber = personHasACar ? 5 : undefined;
 
 </CodeTab>
 
-Later on, when another piece of code receives such value, it'd be forced to handle both cases through [pattern matching](pattern-matching-destructuring.md):
+Later on, when another piece of code receives such value, it'd be forced to handle both cases through [pattern matching](pattern-matching-destructuring):
 
 <CodeTab labels={["ReScript", "JS Output"]}>
 
diff --git a/markdown-pages/docs/manual/object.mdx b/markdown-pages/docs/manual/object.mdx
@@ -8,7 +8,7 @@ order: 7
 
 # Object
 
-ReScript objects are like [records](record.md), but:
+ReScript objects are like [records](record), but:
 
 - No type declaration needed.
 - Structural and more polymorphic, [unlike records](record.md#record-types-are-found-by-field-name).
diff --git a/markdown-pages/docs/manual/overview.mdx b/markdown-pages/docs/manual/overview.mdx
@@ -152,7 +152,7 @@ order: 1
 | --------------------- | --------------------------------------------------------------------------------- |
 | `if (a) {b} else {c}` | `if a {b} else {c}` \*                                                            |
 | `a ? b : c`           | Same                                                                              |
-| `switch`              | `switch` but [super-powered pattern matching!](pattern-matching-destructuring.md) |
+| `switch`              | `switch` but [super-powered pattern matching!](pattern-matching-destructuring) |
 
 \* Our conditionals are always expressions! You can write `let result = if a {"hello"} else {"bye"}`
 
diff --git a/markdown-pages/docs/manual/promise.mdx b/markdown-pages/docs/manual/promise.mdx
@@ -139,7 +139,7 @@ This type signature means that `make` takes a callback that takes 2 named argume
 
 ### Usage
 
-Using the [pipe operator](pipe.md):
+Using the [pipe operator](pipe):
 
 <CodeTab labels={["ReScript", "JS Output"]}>
 
diff --git a/markdown-pages/docs/manual/record.mdx b/markdown-pages/docs/manual/record.mdx
@@ -647,7 +647,7 @@ getAge(kraken)
 getAge(me) // type error!
 ```
 
-The type system will complain that `me` is a `person`, and that `getAge` only works on `monster`. If you need such capability, use ReScript objects, described [here](object.md).
+The type system will complain that `me` is a `person`, and that `getAge` only works on `monster`. If you need such capability, use ReScript objects, described [here](object).
 
 ### Optional Fields in Records Can Be Useful for Bindings
 
diff --git a/markdown-pages/docs/manual/reserved-keywords.mdx b/markdown-pages/docs/manual/reserved-keywords.mdx
@@ -10,7 +10,7 @@ order: 27
 
 > **Note**: Some of these words are reserved purely for backward compatibility.
 >
-> If you _need_ to use one of these names as binding and/or field name, see [Use Illegal Identifier Names](use-illegal-identifier-names.md).
+> If you _need_ to use one of these names as binding and/or field name, see [Use Illegal Identifier Names](use-illegal-identifier-names).
 
 - `and`
 - `as`
diff --git a/markdown-pages/docs/manual/type.mdx b/markdown-pages/docs/manual/type.mdx
@@ -82,7 +82,7 @@ function drawCircle(r) {
 
 </CodeTab>
 
-Note: in the last line, `(~radius as r: int)` is a labeled argument. More on this in the [function](function.md) page.
+Note: in the last line, `(~radius as r: int)` is a labeled argument. More on this in the [function](function) page.
 
 ## Type Alias
 
@@ -289,6 +289,6 @@ var gpa = 2.1 + 10;
 
 Obviously, do **not** abuse this feature. Use it tastefully when you're working with existing, overly dynamic JS code, for example.
 
-More on externals [here](external.md).
+More on externals [here](external).
 
-**Note**: this particular `external` is the only one that isn't preceded by a `@` [attribute](attribute.md).
+**Note**: this particular `external` is the only one that isn't preceded by a `@` [attribute](attribute).
diff --git a/markdown-pages/syntax-lookup/language_dict.mdx b/markdown-pages/syntax-lookup/language_dict.mdx
@@ -8,7 +8,7 @@ category: "languageconstructs"
 
 > Available in v12+
 
-The `dict{}` syntax is used to represent [dictionaries](dict.md). It's used both when creating dicts, and when pattern matching on dicts.
+The `dict{}` syntax is used to represent [dictionaries](dict). It's used both when creating dicts, and when pattern matching on dicts.
 
 ### Example
 
