Detector::Javascript::Sails

package.json listing Sails as a dependency. Sails apps always depend on the sails npm package directly (it is the framework entry point, not a plugin), so a dependency-map hit is a reliable project-level signal even when the file that would carry a source marker (app.js) has been customized or renamed.

Source-side markers. sails.lift( is the canonical bootstrap call every generated app.js/server.js carries; the require/import forms cover apps that construct the app object under a different name before lifting it.

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

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.