4 ms·
also don't forget: - .eslintrc.json to configure ESLint - .prettierignore because it tries to format package-lock.json - prettier.config.json - npm/yarn and
by slimsag 6y ago
also don't forget:
- .eslintrc.json to configure ESLint
- .prettierignore because it tries to format package-lock.json
- prettier.config.json
- npm/yarn and package.json + node_modules
- .nvmrc to pin your node version
- storybook
- renovate to update dependencies
- .editorconfig to ignore node_modules
- mocha for testing and .mochaarc.js
- stylelint and .stylelintrc.json + .stylelintignore
And maybe throw in Jest, tsconfig.json, a gulpfile, and some other stuff.
- eckza 6y agoMy god, I love Elm.
- acid__ 6y agoMaybe it’s just because I was raised on this ecosystem, but in my opinion the sheer amount of incredible functionality you get from all this tooling (at the low price of $0!) is worth 10-15 set-and-forgot files that don’t even show up when you type ls.
- Kovah 6y agoWhile I totally agree that the functionality of most tools is really impressive, this doesn't mean that the current standard of dropping 5 new config files into root for a tool is the best way to handle this. There are ways to do better. It seems that the maintainers of those tools just don't care.
- felbane 6y agoYour comment makes me extremely happy that I haven't needed to deal with anything written in Node. This would drive me absolutely bonkers. Hell, I thought Flask's root directory was getting a bit fluttery with .gitignore, .venv, .flaskenv, __pycache__, and requirements.txt...