The quickest way to build full stack Fuel dApps.
fuels init
— Creates a new fuels.config.ts
file fuels build
— Build forc
workspace and generate Typescript types for everything fuels deploy
— Deploy workspace contracts and save their IDs to JSON file fuels dev
— Start local Fuel Core node and build
+ deploy
on every file change Imagine you have this file structure:
my-fuel-dapp # NextJS app or similar
├── sway-programs # Forc's workspace
│ ├── src
│ ├── ...
│ └── Forc.toml
├── public
│ └── ...
├── src
│ ├── app
│ ├── ...
├ └── sway-programs-api # Type-safe generated API
└── package.json
The Fuel Toolchain and its components (namely forc
and fuel-core
) are pre-requisite for several operations with the Fuels CLI. For example:
fuels build
requires forc
. fuels deploy
requires fuel-core
. Follow the installation guide if you don't have them installed already.
Add it to your my-fuel-dapp
project:
pnpm add fuels@0.97.2
npx fuels@0.97.2 -v
Use fuels init
to create a fuel.config.ts
file.