Developer Tools
Extract JS Decorator Names
Extract decorator names from pasted JavaScript, TypeScript, NestJS, Angular, MobX, or class-based source without executing, compiling, transforming, or uploading code.
0 / 30,000 characters. No upload, storage, or account required.
JS Decorator Names workflows
Use this extractor when copied TypeScript needs a browser-local inventory of NestJS, Angular, ORM, validation, or MobX decorators before migration, dependency cleanup, or QA review.
Audit framework decorators
Pair decorator names with Extract JS Class Names, Extract JS Function Names, and Extract JS Module Specifiers to document controllers, validators, models, and guards.
Review TypeScript shape
Use Extract JS Type Imports, Extract JS Interface Names, and Extract JS Type Aliases.
Clean copied output
Send extracted rows to Sort Lines, Remove Duplicate Lines, or Normalize Whitespace.
What this tool does
Extract JS Decorator Names scans pasted source as text, lists @decorator names with source lines, removes duplicates, and runs locally in your browser.
Common use cases
Extract decorator names from pasted JavaScript, TypeScript, NestJS, Angular, MobX, class-validator, ORM model, test fixture, generated code, or copied source before framework audits, dependency reviews, migration planning, documentation, or QA handoffs.
Use Extract JS Decorator Names when you are working with copied API payloads, logs, encoded values, config snippets, identifiers, or debugging data and need a quick browser-local check before pasting the result into docs, tickets, tests, or another developer tool.
How to use it
- Paste TypeScript, Angular, NestJS, MobX, class-validator, ORM model, test fixture, or copied source that may contain decorators.
- Choose whether duplicate decorator names should be removed and whether extracted names should be normalized for comparison.
- Review extracted decorators with line numbers, then copy the clean list for framework audits, migration notes, dependency reviews, documentation, or handoffs.
Example workflow
Copy a small payload or encoded value from an API response, request URL, log line, or config file. Run the focused check here, confirm the output is readable, then continue with related developer data tools such as validation, formatting, decoding, timestamp conversion, or CSV/JSON conversion.
Privacy note
Extract JS Decorator Names runs locally in your browser. Your pasted code is not uploaded, compiled, transformed, evaluated, executed, stored, or logged.
Practical notes for this tool
Best use case
Use Extract JS Decorator Names when a NestJS, Angular, ORM, validation, or MobX file needs a quick decorator inventory before migration, framework upgrade, dependency cleanup, or QA documentation.
Audit controller decorators before migration
@Controller("/users")
@UseGuards(AuthGuard)
class UsersController {
@Get(":id")
findOne(@Param("id") id: string) { return id; }
}Controller UseGuards Get Param
Privacy and local processing
Decorator extraction stays in your browser. Pasted source is not uploaded, transformed, executed, stored, or logged by ClearUtils.
Limitations to know
- It does not prove how decorators behave at runtime.
- Decorators inside comments or strings may need review.
- Framework-specific metadata still belongs in your codebase or documentation.
Practical FAQ
Does this compile decorators or evaluate metadata?
No. It scans pasted text for decorator names only. It does not compile TypeScript, transform decorators, execute code, or evaluate runtime metadata.
Related workflow links
FAQ
Does Extract JS Decorator Names compile TypeScript?
No. It scans pasted source as text and does not compile TypeScript, transform decorators, execute code, evaluate metadata, upload, store, or log snippets.
Which decorators are included?
It finds common @Decorator and @Namespace.Decorator names in pasted JavaScript, TypeScript, Angular, NestJS, MobX, validator, ORM, and copied-source snippets.
When is this useful?
Use it while auditing framework usage, decorator migrations, dependency cleanup, class model reviews, QA checklists, documentation, or copied-source handoffs.
Explore more tools
Browse the Developer Tools hub or continue with the Developer Data Toolkit when this task is part of a larger workflow.