jo VS hevm

In addition to my previous comment about jq-like tools, I want to share a couple other interesting tools, which I use alongside jq are jo [0] and jc [1].

[0]: https://github.com/jpmens/jo

[1]: https://github.com/kellyjonbrazil/jc

That should recursively list directories, counting only the files within each, and output² jsonl that can be further mangled within the shell². You could just as easily populate an associative array for further work, or $whatever. Unlike bash, zsh has reasonable behaviour around quoting and whitespace too.

¹ https://zsh.sourceforge.io/Doc/Release/User-Contributions.ht...

² https://github.com/jpmens/jo

³ https://github.com/stedolan/jq

I used a handy json utility called jo (sudo yum install jo)

APIs mostly use JSON as their payload. We can easily create them using jo. We can read the command output and put it to your current buffer. For example, we want to create a JSON object with a lower case uuid value for its id property, and a simple name.

I'm a big fan of jo[1] for making generating JSON from the shell not terrible.

[1] https://github.com/jpmens/jo

jo

hevm - written in Haskel

However, since we are using a pure Solidity stack, writing tests with ds-test and running them with dapp.tools or foundry, this was a bit more complicated.

There's also jshon which is a simple stack-based DSL for constructing JSON from shell scripts.

http://kmkeen.com/jshon/

It's written in C and is not actively developed. The latest commit, it seems, was a pull request from me back in 2018 that fixed a null-termination issue that led to memory corruption.

Because I couldn't rely on jshon being correct, I rewrote it in Haskell here:

https://github.com/dapphub/dapptools/tree/master/src/jays

This is also not developed actively but it's a single simple ~200 line Haskell program.

It fits into the stack the same way that Hardhat, Truffle, and Dapp Tools do.

I find it insane that much of Solidity code testing is still happening in external languages. I've recently found https://github.com/dapphub/dapptools and that has blown a lot of my confusion away.

Honourable mention would be https://github.com/dapphub/dapptools for those who prefer UNIX-like tooling, but I'd say for the most part Foundry seems to be the better choice now.

Firstly, I'm warning you that I'm going to shill some amazing things in the Ethereum ecosystem. I would even go so far to say as some of these things are so positive sum and self-evidently public goods that shilling them in the ethereum subreddit should be considered neutral. For example, GitcoinDAO is a place where we all have the permissionless ability to coordinate in building tools and services, like dapptools, for all open-source software, full stop. There's ways to fundraise in public besides joining Discord or sliding into Twitter DM's, like Juicebox. There is a plethora of industry leaders exploring decentralized hosting for bluechip-scale applications, such as Skynet.

If you're into CLI tools - https://dapp.tools/

Dapptools is another framework that has nothing to do with JavaScript.