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: CONTRIBUTING.md
+30-22
Original file line number
Diff line number
Diff line change
@@ -142,13 +142,17 @@ This is usually the file you want to create to test certain compile behavior wit
142
142
- Verify the output, check in the `jscomp/test/my_file_test.ml` and `jscomp/test/my_file_test.js` to version control. The checked in `.js` file is essential for verifying regressions later on.
143
143
- Eventually check in other relevant files changed during the rebuild (depends on your compiler changes).
144
144
145
-
## Contribute to the BS Playground Bundle
145
+
## Contribute to the ReScript Playground Bundle
146
146
147
147
> Note: These instructions are designed for building the 4.06 based version of ReScript (ReScript v6).
148
148
149
149
The "Playground bundle" is the BS compiler compiled to JavaScript, including all necessary dependency files (stdlib / belt etc). It is useful for building tools where you want to compile and execute arbitrary Reason / OCaml in the browser.
150
150
151
-
The ReScript source code is compiled with a tool called [JSOO (js_of_ocaml)](https://ocsigen.org/js_of_ocaml/3.5.1/manual/overview), which uses OCaml bytecode to compile to JavaScript and is part of the bigger OCaml ecosystem. Before we can compile anything, we need to install the required tools (requires [`opam`](https://opam.ocaml.org/doc/Install.html) to be installed):
151
+
The ReScript source code is compiled with a tool called [JSOO (js_of_ocaml)](https://ocsigen.org/js_of_ocaml/3.6.0/manual/overview), which uses OCaml bytecode to compile to JavaScript and is part of the bigger OCaml ecosystem.
152
+
153
+
We actually ship a bytecode version of `js_of_ocaml`, so you actually don't need to install any third party dependencies. This is usually for basic usage if you don't care about the compilation speed or a fast feedback loop (e.g. CI).
154
+
155
+
For faster compilation times, we recommend to install a proper `jsoo` executable:
152
156
153
157
```sh
154
158
# Create the right switch, if not created yet (first install)
@@ -158,18 +162,25 @@ opam switch create 4.06.1
158
162
opam switch 4.06.1
159
163
eval`opam config env`
160
164
161
-
opam install js_of_ocaml.3.5.1
165
+
opam install js_of_ocaml.3.6.0
166
+
```
167
+
168
+
Additionally, make sure to adapt the `scripts/repl.js` file to use the `js_of_ocaml` binary instead (otherwise you'll continue using the slower bytecode version):
The entry point of the JSOO bundle is located in `jscomp/main/jsoo_main.ml` and the script for running JSOO can be found in `scripts/repl.js`. A full clean build can be done like this:
177
+
The entry point of the JSOO bundle is located in `jscomp/main/jsoo_refmt_main.ml` and the script for running JSOO can be found in `scripts/repl.js`. A full clean build can be done like this:
167
178
168
179
```
169
180
# We create a target directory for storing the bundle / stdlib files
170
181
mkdir playground && mkdir playground/stdlib
171
182
172
-
# We build the ReScript source code and also the bytecode for jsoo_main.ml
183
+
# We build the ReScript source code and also the bytecode for jsoo_refmt_main.ml
_Troubleshooting: if ninja build step failed with `Error: cannot find file '+runtime.js'`, make sure `ocamlfind` is installed with `opam install ocamlfind`._
180
191
181
-
**You should now find following files:**
192
+
After a successful compilation, you will find following files in your project:
182
193
183
194
-`playground/exports.js` -> This is the ReScript compiler, which binds the ReScript API to the `window` object.
184
195
-`playground/stdlib/*.js` -> All the ReScript runtime files.
@@ -188,31 +199,28 @@ You can now use the `exports.js` file either directly by using a `<script src="/
188
199
```
189
200
$ node
190
201
> require("./exports.js");
191
-
undefined
192
-
> let compile_result = ocaml.compile(`Js.log Sys.ocaml_version`); // You can change the code here
193
-
undefined
194
-
> eval(compile_result);
202
+
> let compiler = rescript_compiler.make()
203
+
> let result = compiler.rescript.compile(`Js.log(Sys.ocaml_version)`);
204
+
> eval(result);
195
205
4.06.2+BS
196
-
undefined
197
206
```
198
207
199
208
### Playground JS bundle API
200
209
201
-
As soon as the bundle is loaded, you will get access to following functions (as seen in [`jsoo_main.ml`](jscomp/main/jsoo_main.ml)):
210
+
As soon as the bundle is loaded, you will get access to the functions exposed in [`jsoo_refmt_main.ml`](jscomp/refmt/jsoo_refmt_main.ml). Best way to check out the API is by inspecting a compiler instance it either in node, or in the browser:
202
211
203
-
-`window.ocaml`:
204
-
-`compile(code: string)`: Compiles given code
205
-
-`shake_compile(code: string)`: Compiles given code with tree-shaking
206
-
-`compile_super_errors(code: string)`: Compiles given code and outputs `super_errors` related messages on `console.error`
207
-
-`compile_super_errors_ppx_v2(code: string)`: Compiles given code with the React v2 syntax
208
-
-`compile_super_errors_ppx_v3(code: string)`: Compiles given code with the React v3 syntax
209
-
-`load_module(cmi_path: string, cmi_content: string, cmj_name: string, cmj_content: string)`: Loads a module into the compiler (see notes on `cmj` / `cmi` below)
212
+
```
213
+
$ node
214
+
require('./exports.js')
215
+
216
+
> let compiler = rescript_compiler.make()
217
+
> console.log(compiler)
218
+
```
210
219
211
-
For each compile every successful operation will return `{js_code: string}`. On compile errors, the returned object will be `{js_error_msg: string}`.
212
220
213
221
### Working on the Playground JS API
214
222
215
-
Whenever you are modifying any files in the ReScript compiler, or in the `jsoo_main.ml` file, you'll need to rebuild the source and recreate the JS bundle.
223
+
Whenever you are modifying any files in the ReScript compiler, or in the `jsoo_refmt_main.ml` file, you'll need to rebuild the source and recreate the JS bundle.
0 commit comments