Detection

Project types

Type	Meaning
cli	Command-line tool.
library	Exported module/library.
http_server	HTTP server or route-based backend.
unknown	No strong signal found.

Detection signals include:

• package.json with a bin field → cli
• source files with a shebang in common entrypoint files → cli
• process.argv, Bun.argv, or parseArgs usage → cli
• imports from express, fastify, hono, elysia, or @hono/node-server → http_server
• route calls like app.get(...), router.post(...), server.use(...) → http_server
• exported functions, classes, constants, default exports, package.json exports, main, or module → library

HTTP detection wins while scanning source files. CLI package detection via package.json bin wins before source scanning.

Test files

Suitener treats these as test files:

• files under tests/
• files under __tests__/
• *.test.ts, *.test.tsx, *.test.js, *.test.jsx, *.test.mts, *.test.cts
• *.spec.ts, *.spec.tsx, *.spec.js, *.spec.jsx, *.spec.mts, *.spec.cts
• *_test.go

Test commands

Detected in order:

1. package.json scripts.test → bun run test
2. package.json scripts.test:unit → bun run test:unit
3. JS/TS test files → bun test
4. go.mod or Go test files → go test ./...
5. Cargo.toml → cargo test

If no runnable command is detected, check falls back to stub generation.

Ignored directories

• node_modules
• .git
• dist
• build
• suitener-results
• suitener-stubs

Recognized source extensions

• .ts
• .tsx
• .js
• .jsx
• .mjs
• .cjs
• .go
• .rs

Recognized manifests

• package.json
• Cargo.toml
• go.mod