scaffold-eth VS fnm

If you want to learn to develop apps for the EVM (Thats Ethereum, Polygon, xDai, Aurora and many others) then you should read through the code in the various branches of https://github.com/austintgriffith/scaffold-eth for really good full-stack examples

git clone [https://github.com/austintgriffith/scaffold-eth.git](https://github.com/austintgriffith/scaffold-eth.git) challenge-2-token-vendor cd challenge-2-token-vendor git checkout challenge-2-token-vendor yarn install

In this blog post, I’m going to cover the first scaffold-eth speed run project: creating a Staking dApp. If you want to know more about scaffold-eth and my current journey in the web3 world you should read my previous article: My journey in Web3 development: scaffold-eth.

https://github.com/austintgriffith/scaffold-eth is a great ethereum boilerplate project that uses yarn workspaces in a monorepo, its a pretty standard practice that I've seen in the NFT/blockchain dev space.

I'm a fullstack JS developper, i've working and looking heavily into building on ethereum, so this is my first dive into the space. I would love some feeback from more senior devs on this, on the React and Dapp part. It is heavily based on scaffold-eth (and some Uniswap-interface code reading) so I'd recommend starting there if you're starting out rather than my starter, the docs and content there are first class. The stack is just the stack i am used to working with: Tailwind UI, Typescript and Redux Toolkit, and more. I'll be adding more examples other than the Greeter soon. Also i am for hire if you're looking for junior Dapp devs :) Thank your for your time !

Install nodejs: (I highly recommend using a node version manager like fnm) and to install a recent node version (current long term support is 16+)

I highly recommend setting up nodejs with a version manager, nvm was and still is a popular option, however, I now recommend and have been using fnm, a simpler and faster alternative to manage my nodejs versions.

I switched from nvm to fnm a few years ago and have never looked back. Zero performance issues and it supports .nvmrc files.

https://github.com/Schniz/fnm

Are you using some kind of node version manager like fnm?

If it's your terminal that's slow in general and not neovim specifically I found that switching from nvm to fnm for managing node significantly faster at starting up my shell. I don't know whether this is what your issue is but I thought I'd share it regardless. https://github.com/Schniz/fnm

fnm is a fast and simple Node.js version manager. It's really easy to use and is much faster than nvm.

As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.

Install something like Fast Node Manager from https://github.com/Schniz/fnm and install your Node from there. I work in the software field and tend to use the LTS releases for the TypeScript/React projects I work on.

fnm!

You’ll need pnpm and Node.js installed on your machine + some tool for switching node versions (e.g. fnm or nvm will work fine);