feat: standalone fuels node

[petertonysmith94]

• Closes Make fuels node to work without a fuels.config.ts file #3523

Release notes

In this release, we:

• Enabled fuels node to start a fuel-core instance without configuration.

Summary

We can now run a fuel-core node anywhere:

bunx fuels node --fuel-core-port 4000

Checklist

• All changes are covered by tests (or not applicable)
• All changes are documented (or not applicable)
• I reviewed the entire PR myself (preferably, on GH UI)
• I described all Breaking Changes (or there's none)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
fuels-template	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 28, 2025 0:27am
ts-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 28, 2025 0:27am
ts-docs-api	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 28, 2025 0:27am

[github-actions]

Temporary PR

This PR is published in AWS CodeArtifact with version: pr-3813

Install using the below commands — create-fuels variations are commented out.

PNPM

pnpm config set registry https://npm-packages.fuel.network/ --global
pnpm install fuels@pr-3813
# pnpm create fuels@pr-3813

NPM

npm --registry=https://npm-packages.fuel.network/ install fuels@pr-3813
# npm --registry=https://npm-packages.fuel.network/ create fuels@pr-3813

Bun

npm_config_registry=https://npm-packages.fuel.network/ bun install fuels@pr-3813
# npm_config_registry=https://npm-packages.fuel.network/ bun create fuels@pr-3813

[github-actions]

Coverage Report:

Lines	Branches	Functions	Statements
77.35%(+0%)	70.98%(-0.02%)	75.38%(-0.05%)	77.35%(-0.01%)

Changed Files:

Ok	File (✨=New File)	Lines	Branches	Functions	Statements
🔴	packages/account/src/providers/resource-cache.ts	97.95% (+0%)	90% (-5%)	100% (+0%)	97.95% (+0%)
🔴	packages/fuels/src/cli/commands/node/index.ts	92.3% (+4.3%)	83.33% (-16.67%)	100% (+0%)	92.3% (+3.42%)

[arboleya]

I think the idea was that this command would start fuel-core using the default configs that the TS SDK uses internally, but without watching files or re-compiling and re-deploying contracts, etc.

However, now we have forc node (docs), introduced via:

• feat: add forc-node command for easily bootstrapping a node sway#6473

Docs:

• Running a Local Node
• Running a Testnet Node
• Running a Mainnet Node

Examples:

forc node local
forc node testnet
forc node ignition

Because of all the above, I wonder if we still need a fuels node command.

[petertonysmith94]

So remove?

[petertonysmith94]

Or proxy to the forc command?

[arboleya]

Yes, let's remove it and focus on more important stuff.