Rio is a liquid restaking network. Our first product is reETH, which provides access to risk-managed ETH total return without sacrificing liquidity.
This project uses the following technologies and tools:
- PNPM - Package management
- Turborepo - High performance build system
- Foundry - Ethereum development toolkit
- Husky - Git hooks
- Typescript - Type-safe codebase
- Prettier - Code formatter
- Eslint - Code linter
- Nodemon - Development runtime (script monitor)
- Jest - Frontend & backend test suite
- GitHub Actions - CI/CD workflow automation
- Conventional Commits - Commit message standard
A Fast, disk space efficient package manager with native workspace support. PNPM is a drop-in replacement for NPM and Yarn (v1 & v2). It's faster than both and uses less disk space. It has a lockfile that is compatible with both NPM and Yarn. With regard to a monorepo, in most cases, it also serves as a replacement for Lerna.
A high-performance build system for monorepos. Turborepo is a replacement for Lerna and it is mildly faster than Lerna's integrated counterpart Nx. It also requires less configuration and has less of a learning curve compared to Nx if used independently.
It is worth mentioning, along side Nodemon, you can get the same development experience as if you were working with Concurrently to run multiple development scripts or packages local to the repository.
A portable and modular toolkit for Ethereum application development written in Rust.
Foundry consists of:
- Forge: Ethereum testing framework (like Truffle, Hardhat and DappTools).
- Cast: Swiss army knife for interacting with EVM smart contracts, sending transactions and getting chain data.
- Anvil: Local Ethereum node, akin to Ganache, Hardhat Network.
- Chisel: Fast, utilitarian, and verbose solidity REPL.
A modern Git hooks manager.
A superset of JavaScript that compiles to clean JavaScript code. A type-safe coding language and a great tool for large codebases as it helps to prevent bugs and improves code quality.
You will notice 3 tsconfig.ts file variants in the root of the project.
tsconfig.base.json- This is the base configuration for all packages within the monorepo. It is worth pointing out that we extend the recommended rules for the current Node LTS version and for strict type-checking from@tsconfig/node-lts(tsconfig/bases)tsconfig.build.json- This is the configuration for the build process. It extends the base configuration and configures where the compiled codebase should be outputted to and what should be compiled.tsconfig.json- This is the configuration for the root of the monorepo mainly for the IDE to use and other libraries that may need it such as Eslint (@typescript-eslint). It also extends the base configuration.
Within each packages/* directory, you will notice a tsconfig.json and tsconfig.build.json file. This is for package specific Typescript configuration. It is important in some aspects to treat each package independently from each other as they may have different requirements.
For example, the tsconfig.build.json file within a packages/api directory may have its module option set to commonjs. Whereas the tsconfig.build.json file within a packages/frontend directory might have its module option set to esnext.
It is worth mentioning, to improve performance, the incremental option within the tsconfig.base.json has been set to true. This will cache the results of the last successful compilation and use it to speed up the next compilation.
Another configuration that is worth mentioning, is that the declaration option has also been set to true. This will generate .d.ts files for each file within the built dist directory. These files separate out the type information from the compiled code resulting in cleaner code output. This is also faster for the packages that depend on them as the compile doesn't have to sift through the code to find the types.
An opinionated code formatter.
A pluggable and configurable linting tool that statically analyses your code to quickly find problems and can be used to enforce code style.
A monitoring tool that restarts the configured executable when file changes in the configured directory are detected.
Within the packages/* directories, you will notice a nodemode.json that has an executable script of exec: pnpm typecheck && pnpm build. This is to ensure that the codebase is fully type-checked and built - ready for dependents to import. Remember, that the built configuration is only intended for the final built code and not the source code. This form of double Type-checking also quite performant as the Typescript compilation is cached in the form a generate tsconfig.tsbuildinfo file thanks to the incremental: true Typescript configuration option.
A delightful JavaScript Testing Framework with a focus on simplicity. Jest is a great tool for testing your codebase and can be used for both frontend and backend code.
As Typescript does all of the type-checking, there's no requirement to use something like ts-jest to run our files - we would be type-checking twice. Instead, we can lean on SWC, specifically @swc/jest. This is a Jest transformer that uses SWC to compile the Typescript codebase. This is much faster than ts-jest and is also a lot more performant than the default Typescript compiler.
A CI/CD workflow automation tool that is built into GitHub. It is a great tool for automating your workflow and can be used to build, test and deploy your codebase.
It is worth pointing out the .github/workflows/pr.yaml file. This workflow runs on every pull_request and validates the PR title follows the Conventional Commits specification.
A specification for adding human and machine readable meaning to commit messages. It is a great tool for automating your workflow and can be used to build, test and deploy your codebase.
Follow the steps below to set up the monorepo on your local machine for development and testing purposes.
Here's a list of technologies that you will need in order to run this project. We're going to assume that you already have Node.js installed, however, you will need the required version (LTS or v18+) as stated in the package.json:engines.node configuration.
If your computer doesn't already have PNPM installed, you can install it by visiting the PNPM installation page.
If you're using MacOS, you can install it using Homebrew.
brew install pnpmNow that you have PNPM installed, you can install the required Node version by running the following command.
pnpm add -g n
n ltsYou can install the Foundry toolchain installer, Foundryup, by running the following command.
curl -L https://foundry.paradigm.xyz | bashThen follow the instructions on-screen, which will make the foundryup command available in your CLI.
Running foundryup by itself will install the latest (nightly) precompiled binaries: forge, cast, anvil, and chisel. See foundryup --help for more options, like installing from a specific version or commit.
To install all package dependencies, run the following command at the root of the project.
pnpm installTo run all packages, simply run the following command at the root of the project.
pnpm devTurborepo and Nodemon will run each package in parallel and watch for file changes.
There are several ways to deploy this project. Depending on your requirements, here are some examples of some popular methods.
Making use of the pnpm deploy command, we can create a Docker image that only contains the production dependencies for a specific package within the monorepo. This essential bundles the given package and all of its local and external dependencies.
FROM workspace as pruned
RUN pnpm --filter <PACKAGE_NAME> --prod deploy <TARGET_DIRECTORY>
FROM node:18-alpine
WORKDIR /app
ENV NODE_ENV=production
COPY --from=pruned /app/pruned .
ENTRYPOINT ["node", "index.js"]Distributed under the GPL-3.0 License. See the local LICENSE file for more information.