Format Solidity + JS + TS files, pnpm workspace

[bpierre]

The format script is to be ran before merging this PR, whenever we are ready.

[danielattilasimon]

Could we move the formatting into the root of the repo? I know this requires one more pnpm i, but it would let us have a single dprint config for every project in the repo (of which we will inevitably have more than just the contracts).

Also, the dprint plugin for VS Code only works if the config file is in the root directory.

[bpierre]

Good point yes! I am wondering: would it make sense to move to a monorepo now that we have moved to pnpm?

From my experience doing this with pnpm after yarn:

• Doing pnpm i from the root or any of the package does the same thing and installs all the workspaces dependencies (no specific instruction for contributors other than using pnpm).
• Generally, I found pnpm much easier to work with than Yarn 2 & 3 (haven’t tried 4) for monorepos.

I think the only change needed would be to add a package.json and a pnpm-workspace.yaml file at the root level.

[danielattilasimon]

It occured to me too. We should give it a try with pnpm workspaces. The reason I swore off of using a monorepo again was mostly because of Yarn and the nightmare that is package hoisting. Thankfully, pnpm does none of that crap.

[bpierre]

It occured to me too. We should give it a try with pnpm workspaces. The reason I swore off of using a monorepo again was mostly because of Yarn and the nightmare that is package hoisting. Thankfully, pnpm does none of that crap.

I added the change to the PR 🔥

[bpierre]

Also I thought this one would be nice to have for consistency. I also removed useBraces: "always" compared to what we had on frontend/, to be a bit less strict. Also no strong opinion about these two, what do you think @danielattilasimon?