chore: migrate plugins to tsquery

[beaussan]

Migrate:

• astro
• next
• tanstack router

to tsquery to do ast lookup. I didn't to sst given I don't know enough the source file expected shape

This website also help you live debug your tsquery queries: https://tsquery-playground.firebaseapp.com/

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/knip@1009

commit: d6a4883

[webpro]

Thanks, @beaussan! This is super useful to compare bare TS and tsquery side by side.

To be honest, personally I don't find the new queries more readable over bare TS. I think I'd rather write it out and have a bit more flexibility. On the other hand, there's also something to say for not having to call ts.forEachChild and visit.

Happy to have others chime in as well, as I'm a bit on the fence here. It's another thing to learn for folks, or perhaps it's actually preferred over bare TS, idk :)

[beaussan]

This is super useful to compare bare TS and tsquery side by side.

That's the goal!

To be honest, personally I don't find the new queries more readable over bare TS. I think I'd rather write it out and have a bit more flexibility. On the other hand, there's also something to say for not having to call ts.forEachChild and visit.

Happy to have others chime in as well, as I'm a bit on the fence here. It's another thing to learn for folks, or perhaps it's actually preferred over bare TS, idk :)

Totally understandable, at work we have to do a lot of ast based analysis of code files, we started with the same visitor pattern but we end up refactoring to the tsquery pattern a year back and it helped a lot with the maintainability, but it's a tradeoff that only you + team only can consider!

Feel free to close the pr if it's not relevant ✂️

[webpro]

Thanks again Nicolas. I'm going to close this one in favor of implementing resolveAST functions with typescript and some helpers only. We can always reconsider in the future.