Content
@
0 reply
0 recast
0 reaction
frolic
@frolic
$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
2 replies
0 recast
6 reactions
Soptq
@soptq
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
1 reply
0 recast
1 reaction
frolic
@frolic
Does it work in Vercel?
1 reply
0 recast
0 reaction
Soptq
@soptq
Yes it is! Here is the `forge -V` running on Vercel Node.js 20.x. (the last line)
2 replies
0 recast
1 reaction
frolic
@frolic
Is there a way to specify a particular foundry version? Can the npm publish pipeline track it rather than installing latest?
1 reply
0 recast
0 reaction
Soptq
@soptq
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.
1 reply
0 recast
0 reaction
frolic
@frolic
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?
1 reply
0 recast
1 reaction
Soptq
@soptq
Yes, indeed. I have made an update to foundry-up to version 0.1.3 to allow specifying a release tag. For example, if I want to stick to `nightly-2cf84d9f3ba7b6f4a9296299e7036ecc24cfa1da`, I can now: ```bash npm install -g foundry-up --foundry_version=nightly-2cf84d9f3ba7b6f4a9296299e7036ecc24cfa1da ```
1 reply
0 recast
1 reaction
