eslint-config-ns VS shareable-configs

So it's not surprising that I'm pushing the use of Prettier and ESLint in all my projects - and the ones I'm involved in - and taking care of their implementation. As time goes on, it becomes even more important to have a common base of rules and configurations. That's the only way it scales over time. For this reason, I've created both my own Prettier and ESLint configurations. In a now older article on Medium, I explain step by step how to create and reuse your own ESLint configuration.

In this series, we'll cover approaches for managing tooling and how you can implement this yourself to increase your productivity. I'll be using my own personal setup throughout the series as a reference.

Yep, learna takes care of all the versioning and publishing. The scripts to do that are set in package.json and the .github/workflow config takes care of the rest. If you need an example for separate versioing for host and remote, you can leverage what i have here https://github.com/waldronmatt/shareable-configs . Also turbo repo is great if you have a webpack build script to run. It will cache the results so subsequent runs will be extremely quick.