npm-pkg-config

<scope>

Initialize TypeScript projects with proper tooling, type checking, and framework setup.

Reference documentation:

package.md

workspace.md

typescript.md

oxc.md

hono.md

tanstack-spa.md

shadcn-ui.md

dev-tools.md

ci.md

</scope>

<configuration_decisions>

Key Configuration Decisions

Project visibility:

Package structure:

Application type:

Frontend only → TanStack Router + shadcn/ui
Backend only → Hono
Full-stack → Hono + TanStack Router + shadcn/ui
npm library → No framework, focus on build/publish config </configuration_decisions>

<setup_principles>

Required setup sequence (due to configuration dependencies):

Base package (
```
package.md
```
): Foundation for all subsequent configs
Workspace structure (
```
workspace.md
```
): Only if monorepo - must precede package setup
Linting/formatting (
```
oxc.md
```
): Requires package structure to be established
Application setup: Location depends on package structure
- Single package: Root directory
- Workspace: Separate
```
packages/*/
```
  directories
- TypeScript (
```
typescript.md
```
  ): Required for all projects
- Backend:
```
hono.md
```
- Frontend SPA:
```
tanstack-spa.md
```
- UI components:
```
shadcn-ui.md
```
Development tools (
```
dev-tools.md
```
): Requires application structure
CI/CD (
```
ci.md
```
): Final step after all configs established

Location constraints:

Single package: All configs at root
Workspace: Shared configs at root, app-specific in
```
packages/*/
```
</setup_principles>

<reference_index>

Core setup (all projects):

Structure-specific:

Framework-specific:

</reference_index>

<best_practices>

TypeScript:

Package management:

Tooling consistency:

</best_practices>