wevm / anvil.js Goto Github PK

After looking over get-port it seems that a mutex is needed or else there's a chance the same port can be assigned to the different process.

https://github.com/sindresorhus/get-port#beware

await anvil.start();
const simulatorBlockNumber =  await anvil.getBlockNumber();
console.log(simulatorBlockNumber)
await anvil.stop();

gives:

anvil.getBlockNumber is not a function.

How should I interact?

Playwright imports CJS by default in global setup, but it will complain about get-port needing to be dyanmically imported. I made a patch in our repository: https://github.com/sushiswap/sushiswap/blob/master/patches/%40viem__anvil%400.0.6.patch

There is a cjs build but because execa is included and is a js library of type: module cjs doesn't work

await anvil.stop(); does not returns but the service is stopped

Keeping track of various ideas for improvements ...

• Allow specifying a custom binary name (or path), for cases where anvil is not in PATH
• Ability to subscribe to stderr & stdout log output
• Ability to enumerate running anvil instances
• Ability to subscribe to lifetime events (e.g. spawning of new anvil instance in the proxy, errors, etc.)
• Ability to destroy specific anvil instances (e.g. to "force" a full reset between tests)
• Ability to limit number of concurrent anvil instances

Icing on the cake:

• User interface to observe proxy instances (see status / accounts & balances / state, etc. & stream logs)

For anvil itself:

• Ability to preserve & reload full data completely: foundry-rs/foundry#3760

We are currently tracking whether anvil fails to start, but after that, we don't really monitor the underlying anvil process anymore to capture any crashes or exits.