Devin Rhode
Devin Rhode
Lint-staged could do a string replacement or just prepend variable definition to command. Back to the `--shell "/bin/zsh"` option - I don't understand why these scripts aren't _always_ executing inside...
So is passing just `--shell`, without `"/bin/bash"` completely pointless?
FYI I was able to work-around this issue using this method: https://stackoverflow.com/a/65321060/565877
So... work-arounds... simplest that has worked for me is to temporarily re-write code so that it does not use dynamic imports... Maybe there could be a codemod that does this...
Of course, a codemod might work best if the arguments to `import(` are static (not determined at runtime) This is a lot easier to handle: ``` const FooPage = ()...
Not encountering any errors, just being picky 😊 One benefit would be faster npm installs. How does XO detect ava test files? `*.test.*`? (This would certainly catch more than ava...
Maybe we could check if ava is installed in package.json, at least then the rules aren't loaded, and presumably, no parsing import statements. Still have the npm install waste, though....
Interesting. How can XO know what compiler settings have any effect on the TS ESLint plugin? The project could export an object type 💡 This gets me thinking, What if...
@sindresorhus @Spence-S @fisker - any thoughts?
I am indeed using lint-staged only on changed files. Something that may be a game-changer, which I just recently discovered, are TS project references. I haven't gone down this rabbit...