Respect the XDG base directory specification

Hello,

I searched in the issues here and shockingly I haven’t found this mentioned.

Currently, cosmiconfig searches up the parent tree from the working directory, stopping at $HOME, which is fine and most, I would assume, are okay with this.

However, for filesystem psychopaths like myself, it pains me to have to move any sort of user configuration file out $XDG_CONFIG_HOME/project-name/ directory (usually, ~/.config/project-name/) and pollute my home directory.

Any thoughts on adding this as a final search path?

You can read up on the specification here and here.

In short, using prettier as an example, I’d imagine the workflow to go like this…

1. Perform the current lookup traversal as it is done right now.
2. If nothing found, check the following:

• $XDG_CONFIG_HOME/prettier/config
• $XDG_CONFIG_HOME/prettier/[...current standard file name checks]

Thanks for considering.

[davidtheclark]

Reopening the issue to encourage more people to chime in.

[jasonkarns]

Strong agree that searchPlaces should default to XDG compliance. Library authors (by and large) will not change the defaults. So cosmiconfig’s defaults will perpetuate to all users of all libs which use cosmicconfig. In one swift PR, cosmiconfig could give control to all the users of all the cosmic-dependent libs by just making searchPlaces default to XDG’s directories.