Simen Bekkhus
Simen Bekkhus
Note that this issue is specifically about the code generated by `@tanstack/router-generator` output into the user's code base, not necessarily the router's own code base. (in theory, this _might_ improve...
5.5 is out btw, and this issue is blocking me from adopting the new flag
The exported value (i.e. `routeTree`) would need to be explicitly typed rather than inferred.
Why is that not possible? If it's able to be inferred, it should be possible to generated as well. If nothing else, you can use `tsc` itself to output the...
Can this land in the meantime? 🙂 I agree tests to prevent regressions is ideal, but this doesn't hurt on its own, and allows me to drop a floated patch
Yeah, no rush at all 👍 Thanks!
Workaround, if people need it: ```js import { fixupPluginRules } from '@eslint/compat'; import * as eslintPluginTanstackQuery from '@tanstack/eslint-plugin-query'; export default [ { plugins: { '@tanstack/query': fixupPluginRules(eslintPluginTanstackQuery), }, rules: eslintPluginTanstackQuery.configs.recommended.rules, },...
This seems like a missing dependency (or package manager bug) as we depend on a CJS version of chalk. Do you have a reproduction?
I think it makes sense to align, but I'll defer to @georgekaran
I wonder if we should just ditch shelling out to `find` always. Crawling in JS is way faster (as long as ignores are sane, which they usually are). --- I...