foundry-on-npm's Introduction

@foundryup/foundry

Install

This package follows foundryup's nightly releases, so you can install the latest nightly with:

npm install @foundryup/foundry

Or a specific nightly release with:

npm install @foundryup/[email protected]

Usage

{
  "scripts": {
    "build": "forge build"
  },
  "devDependencies": {
    "@foundryup/foundry": "0.2.0-nightly.c631cf3"
  }
}

% npm forge --version

forge 0.2.0 (c631cf3 2024-02-18T00:17:43.475108000Z)

Troubleshooting

GLIBC errors on Vercel

/vercel/path0/node_modules/.pnpm/@foundryup/[email protected]/node_modules/@foundryup/foundry/bin/foundry/linux_amd64/forge: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /vercel/path0/node_modules/.pnpm/@foundryup/[email protected]/node_modules/@foundryup/foundry/bin/foundry/linux_amd64/forge)

You can resolve this by changing your Vercel app's Node.JS version to 20.x.

foundry-on-npm's People

Contributors

Stargazers

foundry-on-npm's Issues

add windows support

I had to remove these due to npm package size limits and win32 wasn't part of the wrapper shell scripts anyway.

separate packages per binary (forge, anvil, etc.)

it would be nice if we had separate packages like @foundryup/forge and @foundryup/anvil so users could optionally install just the ones they need/use

and then turn @foundryup/foundry into a "wrapper" around all of these smaller deps

this would also help with package size limits noted in #1