Code TypeScript utilities
Package metadata, imports, CSS and file names. Explore focused implementations with runnable browser demos, source links and installation notes.
Topic hub
Useful tools for package metadata, imports, css and file names
This collection groups 7 independent TypeScript utilities around one developer task. Read each summary, open a live demo, then inspect the repository, tests and release details before adopting a package. The pages document current behavior and do not claim compatibility with an earlier abandoned source.
Code packages
Start with the capability that matches the input or workflow you need to inspect.
- import-specifier-scan-kit Scan JavaScript source text for import, export, dynamic import and require specifiers. Includes package-name helpers for dependency previews and audits.
- node-lockfile-doctor-kit Inspect Node package-manager lockfile consistency with structured diagnostics. Preview catches package-manager drift, missing locks and lockfile conflicts.
- package-author-parse-kit Parse package author, maintainer and contributor strings with stable diagnostics. Preview exposes name, email, URL tokens and source offsets for package metadata editors.
- css-font-shorthand-kit Parse and format CSS font shorthand values with structured diagnostics. Small browser-friendly parser for design-token and editor tooling.
- css-media-query-match-kit Parse and match small CSS media query lists with stable diagnostics. Preview evaluates responsive rules against explicit viewport environments.
- filepath-validator-kit Validate file path strings with portable, POSIX or Windows policies and structured diagnostics. Form-friendly validation with segment spans, stable issue codes and reusable policies.
- file-extension-inspect-kit Inspect filename extensions with explicit dotfile, extensionless and compound-extension policies. Preview shows dotfile handling, compound extension matching and comparison behavior.
Evaluate before you adopt
Every package page links to its public GitHub source, tests, CI and npm status. Use the browser demo for a quick representative check, then pin the version and validate edge cases against your own data. Maintainer accountability and the current repository remain the source of truth for defects, limits and support.
Read the method and limits