This project shows a minimal fullstack ReasonML application. It has a
- Backend web server that compiles to a native binary using the Esy/dune compilation toolchain
- Frontend ReasonReact component that compiles to JavaScript using the BuckleScript toolchain
- Shared business logic used by both of the above
This is a proof-of-concept; you can customize it to your needs.
At the moment unfortunately the backend may not work on Windows due to an issue with a dependency. I am trying to resolve it.
Follow these steps:
- Install NodeJS (one-time setup)
- Install Esy (one-time setup):
npm install --global esy@latest
- Set up the backend project:
esy install
(one-time setup but will take a while to compile dependencies like SSL so grab your favourite beverage) - Run the backend app:
esy b dune exec backend/App.exe
- In another terminal, build frontend:
a.
npm install
(or use pnpm to save some disk space) b.npx bsb -clean-world
c.npx bsb -make-world
- Run the frontend (this is in development mode):
npm run server
- Browse the frontend: http://localhost:8000/
You can also try out the app without the Webpack dev server:
- Assuming the above builds have already been done
- Put production assets in the
build
directory:npm run webpack:production
- Run the backend app:
esy b dune exec backend/App.exe
- Browse the frontend (note, different port than above, this is being served directly from the backend app): http://localhost:8080/
Correctly caches the JS bundle–with cache busting!
This project pulls together:
- A working setup of the ReWeb Reason/OCaml native web framework
- A ReasonReact frontend app, using the BuckleScript OCaml-to-JS compiler
These are the significant parts of the project:
backend/
: contains the sources for the backend executableesy.lock/
: a lock directory used by Esy to capture precise dependency informationfrontend/
: contains the sources for the frontend ReasonReact appshared/
: contains sources shared between the backend and frontendbsconfig.json
: BuckleScript project configurationdune-project
: Dune project configuration (for the native build)esy.json
: Esy project configuration (native package management)fullstack-reason.opam
: OPAM project configuration (empty but needed for backward-compatibility with OPAM)package.json
: Npm project configurationwebpack.config.js
: Webpack bundler configuration for the frontend
Honourable mention: build outputs are in the .gitignore
.