What would you consider to be a must for a modern 2022 dev stack?

• Enzyme

  32 19,967 6.7 JavaScript

  JavaScript Testing utilities for React

  

react testing library instead of enzyme for testing react UIs. I'll never go back.

• react-query

  190 27,869 9.1 TypeScript, JS

  Discontinued 🤖 Powerful asynchronous state management, server-state utilities and data fetching for TS/JS, React, Solid, Svelte and Vue. [Moved to: https://github.com/TanStack/query]

  

react-query is pretty neat too. I default to that for most projects unless it's something unusual

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• semgrep

  74 9,688 9.9 OCaml

  Lightweight static analysis for many languages. Find bug variants with patterns that look like source code.

  

One of the tools Ilai Fallach recommended to me was Semgrep it looks really interesting in terms of enforcing coding standards - did any of you guys ever try that?

• go-getting-started

  12 43 4.9 Go

  Develop Go Apps in Kubernetes with Okteto (by okteto)

  

We use something called Okteto to see local react changes running against a fairly complex Kubernetes setup. Not sure if it will suit your needs but it works well for us ATM.

• dotfiles

  15 48 9.1 Nix

  Configuring the universe with Nix. (by samhh)

With Nix we have a shell.nix in the root of our repo describing all of the project's system dependencies. It looks something like this. You can pin nixpkgs with Flakes (think lockfiles) or by hardcoding a specific revision. We do the latter because I didn't want to complicate the Nix install for everyone by requiring they enable experimetnal features.

• direnv

  157 11,675 8.7 Go

  unclutter your .profile

  

Now, whenever anyone - on Linux or macOS - enters the project's Nix shell they'll share the same versions of all the same dependencies. Nix handles this all automatically, and it's no problem if two projects want two different versions of the same package. I generally also recommend that people use direnv so they can keep using their shell and have changes to shell.nix automatically picked up.

Suggest a related project