Use .res.js instead of .bs.js

pages/docs/manual/latest/build-configuration.mdx

@@ -34,6 +34,7 @@ Your source files need to be specified explicitly (we don't want to accidentally
   "sources": ["src", "examples"]
 }
 ```
+
 ```json
 {
   "sources": {
@@ -59,22 +60,22 @@ You can mark your directories as dev-only (for e.g. tests). These won't be built
 
 ```json
 {
-  "sources" : {
-    "dir" : "test",
-    "type" : "dev"
+  "sources": {
+    "dir": "test",
+    "type": "dev"
   }
 }
 ```
 
-You can also explicitly allow which modules can be seen from outside. This feature is especially useful for library authors who want to have a single entry point for their users.   
+You can also explicitly allow which modules can be seen from outside. This feature is especially useful for library authors who want to have a single entry point for their users.  
 Here, the file `src/MyMainModule.res` is exposed to outside consumers, while all other files are private.
 
 ```json
 {
   "sources": {
     "dir": "src",
     "public": ["MyMainModule"]
-  },
+  }
 }
 ```
 
@@ -140,7 +141,8 @@ This configuration only applies to you, when you develop the project. When the p
 ## suffix
 
 **Since 11.0**: The suffix can now be freely chosen. However, we still suggest you stick to the convention and use
-one of the following:  
+one of the following:
+
 - `".js`
 - `".mjs"`
 - `".cjs"`
@@ -151,16 +153,15 @@ one of the following:
 - `".bs.mjs"`
 - `".bs.cjs"`
 
-Currently prefer `.bs.js` for now.
+Currently prefer `.res.js` for now.
 
 ### Design Decisions
 
-Generating JS files with the `.bs.js` suffix means that, on the JS side, you can do `const myReScriptFile = require('./theFile.bs')`. The benefits:
+Generating JS files with the `.res.js` suffix means that, on the JS side, you can do `const myReScriptFile = require('./theFile.bs')`. The benefits:
 
 - It's immediately clear that we're dealing with a generated JS file here.
 - It avoids clashes with a potential `theFile.js` file in the same folder.
 - It avoids the need of using a build system loader for ReScript files. This + in-source build means integrating a ReScript project into your pure JS codebase **basically doesn't touch anything in your build pipeline at all**.
-- [genType](/docs/gentype/latest/introduction) requires `bs.js` for compiled JS artifacts. If you are using `genType`, you need to use `bs.js` for now.
 
 ## uncurried
 

pages/docs/manual/latest/converting-from-js.mdx

@@ -82,9 +82,9 @@ Add this file to `rescript.json`:
   },
 ```
 
-Open an editor tab for `src/Main.bs.js`. Do a command-line `diff -u src/main.js src/Main.bs.js`. Aside from whitespaces, you should see only minimal, trivial differences. You're already a third of the way done!
+Open an editor tab for `src/Main.res.js`. Do a command-line `diff -u src/main.js src/Main.res.js`. Aside from whitespaces, you should see only minimal, trivial differences. You're already a third of the way done!
 
-**Always make sure** that at each step, you keep the ReScript output `.bs.js` file open to compare against the existing JavaScript file. Our compilation output is very close to your hand-written JavaScript; you can simply eye the difference to catch conversion bugs!
+**Always make sure** that at each step, you keep the ReScript output `.res.js` file open to compare against the existing JavaScript file. Our compilation output is very close to your hand-written JavaScript; you can simply eye the difference to catch conversion bugs!
 
 ## Step 3: Extract Parts into Idiomatic ReScript
 
@@ -225,9 +225,9 @@ exports.queryResult = queryResult;
 
 We hurrily typed `school` as a polymorphic `'whatever` and let its type be inferred by its usage below. The inference is technically correct, but within the context of bringing it a value from JavaScript, slightly dangerous. This is just the interop trick we've shown in the [`external`](external) page.
 
-Anyway, the file passes the type checker again. Check the `.bs.js` output, diff with the original `.js`; we've now converted a file over to ReScript!
+Anyway, the file passes the type checker again. Check the `.res.js` output, diff with the original `.js`; we've now converted a file over to ReScript!
 
-Now, you can delete the original, hand-written `main.js` file, and grep the files importing `main.js` and change them to importing `Main.bs.js`.
+Now, you can delete the original, hand-written `main.js` file, and grep the files importing `main.js` and change them to importing `Main.res.js`.
 
 ## (Optional) Step 5: Cleanup
 
@@ -283,7 +283,7 @@ We've:
 - typed the payload as a record with only the `student` field
 - typed `getStudentById` as the sole method of `student`
 
-Check that the `.bs.js` output didn't change. How rigidly to type your JavaScript code is up to you; we recommend not typing them too elaborately; it's sometime an endless chase, and produces diminishing returns, especially considering that the elaborate-ness might turn off your potential teammates.
+Check that the `.res.js` output didn't change. How rigidly to type your JavaScript code is up to you; we recommend not typing them too elaborately; it's sometime an endless chase, and produces diminishing returns, especially considering that the elaborate-ness might turn off your potential teammates.
 
 ## Tips & Tricks
 

pages/docs/manual/latest/interop-with-js-build-systems.mdx

@@ -33,14 +33,14 @@ You can make ReScript JS files look even more idiomatic through the in-source +
     "module": "commonjs", // or whatever module system your project uses
     "in-source": true
   },
-  "suffix": ".bs.js"
+  "suffix": ".res.js"
 }
 ```
 
 This will:
 
 - Generate the JS files alongside your ReScript source files.
-- Use the file extension `.bs.js`, so that you can require these files on the JS side through `require('./MyFile.bs')`, without needing a loader.
+- Use the file extension `.res.js`, so that you can require these files on the JS side through `require('./MyFile.bs')`, without needing a loader.
 
 ## Use Loaders on ReScript Side
 

pages/docs/react/latest/router.mdx

@@ -84,10 +84,10 @@ let make = () => {
 ```
 ```js
 import * as React from "react";
-import * as User from "./User.bs.js";
-import * as RescriptReactRouter from "@rescript/react/src/RescriptReactRouter.bs.js";
-import * as Home from "./Home.bs.js";
-import * as NotFound from "./NotFound.bs.js";
+import * as User from "./User.res.js";
+import * as RescriptReactRouter from "@rescript/react/src/RescriptReactRouter.res.js";
+import * as Home from "./Home.res.js";
+import * as NotFound from "./NotFound.res.js";
 
 function App(Props) {
   var url = RescriptReactRouter.useUrl(undefined, undefined);