What's the current feeling about putting config file stuff (assuming it's not crazy huge) into `package.json`? Love it? Hate it? I'm just not wildly crazy about adding YACF (yet another config file) to the project top level directory. And my config is maybe ~10 lines long? - ThreadSky

jherr.dev • 13 days ago

What's the current feeling about putting config file stuff (assuming it's not crazy huge) into `package.json`? Love it? Hate it? I'm just not wildly crazy about adding YACF (yet another config file) to the project top level directory. And my config is maybe ~10 lines long?

Comments

mrclay.org•13 days ago

“Gosh that’s lots of config files” at least reminds us of the maintenance cost of adding yet another tooling dependency. 🤷

mrclay.org•13 days ago

Separate files, and switching away from json if I need comments/logic in config.

raix.dev•13 days ago

Same, small configs like postcss/husky etc. in package.json - I wish we could have a .config folder or file dedicated/ maybe even with a convention matching package names (reading config schemas from packages…)

larsgraubner.bsky.social•13 days ago

I liked the idea, but as soon as they get more complex, need dynamic (js) config it fails fast. So I‘m team YACF 🤷‍♂️

itsjavi.com•13 days ago

I feel the list of config files we need for large projects becomes too large. I wish tooling supported a ".config" directory where to put their config files, as an alternative.

faithfinder.bsky.social•13 days ago

Either put all your configs in package.json or none. Otherwise it's just confusing. Seeing how eslint doesn't support package.json config anymore, my answer is "none"

alexkates.dev•13 days ago

its a crappy situation all around but at least with YACF you can get type checking.... normally.

jacobpackert.dk•13 days ago

I’m actually okay with just having so so many config files. When I have a ton of folders/files in the repo I don’t see the config files in the file panel. They’re easy to visually grep. Config as .js/.ts/.mts is much more powerful than what’s possible in .json.
And maybe better for AI suggestions?

sheraff.bsky.social•13 days ago

If you add to `package.json`, will it have auto-completion based on the json schema? (which many json configs have). Will it work well with a `package.json` linter like `eslint-plugin-package-json`? For me, a separate file is always better.

Comments

Posting Rules

Reply