Spencer Snyder

> [@spence-s](https://github.com/spence-s) Could XO check if `typescript-eslint` rules are being applied to JS files, and use the TS parser for all files in only those cases, or maybe use the...

Its part of cosmiconfig loading - we should potentially document this since it might trip up other file watching tools. https://github.com/cosmiconfig/cosmiconfig/blob/main/src/loaders.ts#L118

hmm it might be good default behavior, but I think I can imagine a scenario where you have a config stub or fixture that you do want to watch, so...

Hey @tommy-mitchell thanks for the bug report. This is likely due that we watch certain globs of files that the next js dev process copies while running/changing things. You can...

So I created a nextjs project to test. I don't really use it myself, and I could NOT reproduce this issue on mac. I did not even need to add...

I recently had to work on a `Next` project and I did notice this happening some. The current fix is to ignore both the `.next` and the `.vercel` folder. ```...

I don't really have a strong opinion on where the base config ends up, so I am happy either way if it stays in `xo` or if its moved `eslint-config-xo`......

Note that with the next version you can "eject" by: If you want to use all the plugins: `eslint.config.js` ``` import xo from 'xo'; export default await xo.xoToEslintConfig(); // this...

Share your configs, we cannot help otherwise: Ignores should be in a config of their own, ie... ``` export default = [ {ignores: '**/my-ignores/**'}, // ignore is the ONLY key...

@nadeemc Thanks for that!!! This is a bug with xo currently due to rapid changes in eslint. I believe it will work correctly with you remove the "name" field. (We...