3 ms·
When you're at the point of needing to configure a tool which handles a base config, you need to learn the underlying tools anyway at that point, but without th
by insin 10y ago
When you're at the point of needing to configure a tool which handles a base config, you need to learn the underlying tools anyway at that point, but without the experience of having built the base config up.
Keeping config directly in a project creates a maintainability issue once you have a number of projects on the go, as you then need to turn it into a module like create-react-app's react-scripts or else it's copy and paste time, which becomes horrible across multiple projects, especially if you're evolving your config as you learn.
Has anyone written a guide or supporting tools for creating your own config as a reusable module from the beginning? It feels like there's a gap which needs filled there.
- cobralibre 10y ago> Has anyone written a guide or supporting tools for creating your own config as a reusable module from the beginning? It feels like there's a gap which needs filled there. It looks like you did! https://github.com/insin/ad-hoc-reckons/blob/master/CreatingReusableDevelopmentTooling.md https://github.com/insin/ad-hoc-reckons/blob/master/Creating...