Create a dev container for the `create-fuels` template app on Stackblitz

[Dhaiwat10]

It could be worth having a Stackblitz template for the create-fuels template app. This will be a fullstack Fuel dev container that works fully in the browser.

We should mention this in our docs if we create one such container, as well as using it in the bug issue template.

[maschad]

We will probably want to have this running against a Testnet fuel node, so we can re-address this once that's live.

[danielbate]

We can unblocked this now due to devnet.

[arboleya]

Ideally, we should be able to run fuel-core and forc on Stackblitz. 🙃

Simple things:

// package.json
{
  "devDependencies": {
    "@fuels/forc": "0.60.0",
    "@fuels/fuel-core": "0.30.0",
  }
}

If we'd cross-publish fuelup:

// package.json
{
  "scripts": {
    "install": "fuelup default testnet",
  },
  "devDependencies": {
    "@fuels/fuelup": "0.26.0"
  }
}

# fuel-toolchain.toml
[toolchain]
channel = "testnet"

[components]
forc = "0.60.0"
fuel-core = "0.30.0"

We should consider approximating the Rust and NodeJs ecosystems.

Cross-publishing some crates to NPM could be a start. 🙂

[petertonysmith94]

// package.json
{
  "devDependencies": {
    "@fuels/forc": "0.60.0",
    "@fuels/fuel-core": "0.30.0",
  }
}

We don't publish these binaries anymore.

[arboleya]

Yes, we should consider approximating the Rust and NodeJs ecosystems.

Cross-publishing crates to NPM could be a good start. 🙂

Just like it happens with fuel-asm (source).

[petertonysmith94]

Yes, we should consider approximating the Rust and NodeJs ecosystems.

Cross-publishing crates to NPM could be a good start. 🙂

Just like it happens with fuel-asm (source).

Thanks for the insight - need to take a better look at this repo!

[danielbate]

Marking as blocked as this topic is being investigated by product.

[arboleya]

Let's close for now.