m1-terraform-provider-helper VS fnm

There's virtually no unsolved issue. If you need something x86 is you use rosetta. If you're using terraform and a provider hasn't issued an ARM release you can use the m1 provider helper.

There really isn't any substitute for production experience. Yes you can learn the basics, and the universals are transferable, but you're never going to come across e.g. something like needing this in a homelab, still less the real reasons why you need it...

Try this. https://github.com/kreuzwerker/m1-terraform-provider-helper

tfswitch might help with particular issue of terraform versioning:

https://tfswitch.warrensbox.com/

Even then some versions of terraform providers are not compatible with M1 macs. Docker would help with that probably, but so can: https://github.com/kreuzwerker/m1-terraform-provider-helper

Perhaps these sort of issues support the benefits of per-module docker images?

Check to see if your provider has an M1 compiled version https://github.com/kreuzwerker/m1-terraform-provider-helper/blob/main/docs/provider_information.md

The general availability of darwin_arm64 Terraform providers. There are often cases where the maintainers did not release a darwin_arm64 version yet. Only roughly a fourth of all providers have a darwin_arm64 version released (see here for details)

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);