class Detector::Typescript::TanstackRouter

Defined in:

detector/detectors/typescript/tanstack_router.cr

Constant Summary

SIGNAL = Regex.union(/from\s*['"]@tanstack\/(?:[a-z]+-)?router['"]/, /require\(\s*['"]@tanstack\/(?:[a-z]+-)?router['"]\s*\)/, /\bcreateFileRoute\s*\(/, /\bcreateLazyFileRoute\s*\(/, /\bcreateRootRoute(?:WithContext)?\s*[(<]/)

Single precompiled alternation — one PCRE2 scan over the file.

createRouter( and createRoute( used to be listed here as standalone markers, and both are ordinary names other routers own: createRouter({ history, routes }) is the Vue Router 4 entry point, Solid Router exports the same name, and tRPC v9's generated createRouter() helper carries it too. Every Vue 3 project with a TypeScript router module was therefore reported as TanStack Router and paid for a TanStack analyzer pass that had nothing to extract.

Nothing is lost by dropping them: a file that calls either factory has to import it from @tanstack/*router in that same file, which the import branches below match. Those branches no longer demand the import keyword on the same line as the specifier either, so a formatter-wrapped multi-line import (import {\n createRoute,\n} from '@tanstack/react-router') is matched rather than relying on the bare factory names to carry it.

The package pattern covers every TanStack Router adapter (@tanstack/react-router, /solid-router, /svelte-router, the bare /router) without reaching @tanstack/react-router-devtools, which the required closing quote excludes.

createFileRoute / createRootRoute stay: they are TanStack's own file-based routing API and have no other owner.

Class Method Summary

Instance Method Summary

Instance methods inherited from class Detector

applicable?(filename : String) : Bool applicable?, base_relative_path(filename : String) : String base_relative_path, content_matches?(file_contents : String, markers : Regex) : Bool content_matches?, detect(filename : String, file_contents : String) : Bool detect, gemfile_dependency?(file_contents : String, gem_name : String) : Bool gemfile_dependency?, gemspec_dependency?(file_contents : String, gem_name : String) : Bool gemspec_dependency?, idempotent? : Bool idempotent?, logger : NoirLogger logger, name : String name, path_sensitive? : Bool path_sensitive?, record_unparsable_document(filename : String, error : Exception) : Nil record_unparsable_document

Constructor methods inherited from class Detector

new(options : Hash(String, YAML::Any)) new

Macros inherited from class Detector

detector_for(tech, extensions = nil, basenames = nil, path_segments = nil, idempotent = nil) detector_for

Class Method Detail

def self.tech_name : String #

The tech name without needing an instance, so the registry can be read off the classes themselves rather than from a parallel list.


[View source]

Instance Method Detail

def applicable?(filename : String) : Bool #
Description copied from class Detector

Cheap filename-only filter the detector pass uses to skip #detect on files the detector cannot possibly match. The default true preserves prior behavior (every detector runs on every file). Override with the same predicate the body of #detect starts with — e.g., filename.ends_with?(".py") for a Python framework detector — so the detector loop avoids the #detect dispatch on files outside the detector's language.

On large codebases (saleor's 4255 .py files) this lifts ~100 virtual #detect calls per file out of the hot loop because most detectors' inner first-line is exactly this kind of cheap filename check.


[View source]
def detect(filename : String, file_contents : String) : Bool #

[View source]
def set_name #

[View source]