thinking of putting up a $500 USDC bounty for vercel-compatible foundry binaries

I want to be able to run `forge build` in my vercel app's "build command" setting and use the resulting output files (e.g. bytecode, ABIs) in my vercel app

any takers?

$500 USDC bounty to publish Foundry binaries to npm

The npm package should be automated and track upstream versions (e.g. nightly)

Ultimately I want to be able to run `forge build` in my Vercel app’s “build command” setting and use the resulting output files in my app (ABI, bytecode, etc.)

@bountybot

Post bounties and services on Farcaster by tagging me. Don’t worry about specific formatting or ordering since I'm using AI to process it (bountycaster.xyz) /bounties. FAQ: bountycaster.xyz/FAQ

Just made one 🫡 :

```bash
npm install -g foundry-up
```
and you can `forge build` with latest nightly foundry without problems.

Source code:

hypertext veteran • /mud core dev @lattice

Just made one 🫡 :

```bash
npm install -g foundry-up
```
and you can `forge build` with latest nightly foundry without problems.

Source code: https://github.com/Soptq/foundry-up

Probably a full-stack, mainly focusing on Distributed System / Consensus / Privacy-preserving Tech etc. Decentralization is a trend, privacy must be protected.

Yes it is! Here is the `forge -V` running on Vercel Node.js 20.x. (the last line)

Is there a way to specify a particular foundry version? Can the npm publish pipeline track it rather than installing latest?

For now there isn't, as Foundry still has no versioned releases (see https://github.com/foundry-rs/foundry/issues/3895 for more details).

However, this functionality is not hard to implement once the Foundry has versioned releases. Will add this feat when its ready.

There may be no versioned releases, but foundryup lets you specify commits, which has let us pin to specific points in time if there are temporary bugs and we need to roll back while we wait for upstream fixes.

How would you go about that in the npm package?