Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Global configuration #250

Closed
niftylettuce opened this issue Sep 1, 2017 · 7 comments
Closed

Global configuration #250

niftylettuce opened this issue Sep 1, 2017 · 7 comments

Comments

@niftylettuce
Copy link

My defaults are very different than the normal xo defaults. Sometimes I mock up some JavaScript in a file in its own folder and would prefer to have a ~/.xoconfig with default options/overrides. Is this possible? I see there's a ~/.xo-cache but is there a ~/.xorc or something similar?

@lfades
Copy link

lfades commented Sep 12, 2017

I would really like to see this too, xo is actually 31 % of my package.json and it was very large before

@sindresorhus
Copy link
Member

@goluis You could make a shareable config with your overrides.

@kevva
Copy link
Contributor

kevva commented Sep 13, 2017

@sindresorhus, would still need to add it to extends in package.json every time?

@sindresorhus
Copy link
Member

I was referring to the 30% comment. It would at least reduce it to a couple of lines.

@sindresorhus
Copy link
Member

sindresorhus commented Nov 9, 2017

I'm open to a global XO config if someone does a good pull request with docs and tests.

The file should live in https://github.com/sindresorhus/env-paths#pathsconfig as xo.json.

@sindresorhus
Copy link
Member

sindresorhus commented Nov 9, 2017

Hmm, actually, would probably be better to just resolve a globally installed sharable config and use that. Then it's exactly like having a local shareable config but falls back to the global one if a local one is not found. So to have a global fallback, you would just have to do npm i -g eslint-config-foo. That way you only need maintain one override config in one place.

@fregante
Copy link
Member

fregante commented Jan 4, 2023

Closing as per last comment (an because it's a little old and #448 would be a more explicit solution)

@fregante fregante closed this as not planned Won't fix, can't repro, duplicate, stale Jan 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants