A non-NextJs app will be available once this issue is resolved
Getting started with Fuel as a frontend or fullstack developer is as simple as:
To install the Fuel toolchain, you can use the fuelup-init script.
This will install forc, forc-client, forc-fmt, forc-lsp, forc-wallet as well as fuel-core in ~/.fuelup/bin.
curl https://install.fuel.network | shHaving problems? Visit the installation guide or post your question in our forum .
If you're using VSCode, we recommend installing the Sway extension .
fuelup installed? If you already have fuelup installed, run the commands below to make sure you are on the most up-to-date toolchain.
fuelup self update
fuelup update
fuelup default latest You can generate a full-stack counter dapp in seconds with the create fuels CLI:
pnpm create fuels Move into the project directory. Assuming you named the project my-fuel-project, you can run:
cd my-fuel-projectNext, run the following command to start a local development node:
pnpm fuels:dev The local endpoint for node will be http://localhost:4000/v1/graphql.
Next, open a new terminal in the project directory, and run the following command to start the frontend:
pnpm dev The frontend will be running at http://localhost:3000 .
While the local node is running, any changes you make to the Sway contract inside the sway-contract folder will automatically trigger several updates:
forc build command. forc deploy command . contract-ids.json with the new contract ID will be generated in the src/sway-api folder. This means you don't need to worry about updating the contract ID, ABI, or TypeScript types while you develop.
Ready to learn more? Check out the following resources: