open-index/open-npm huggingface dataset:
npm package: @prachiti.paluskar/custom-datepicker
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 8.2.14.
Latest version: 0.0.1

# CustomDatepicker

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 8.2.14.

## Code scaffolding

Run `ng generate component component-name --project custom-datepicker` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project custom-datepicker`.
> Note: Don't forget to add `--project custom-datepicker` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build custom-datepicker` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build custom-datepicker`, go to the dist folder `cd dist/custom-datepicker` and run `npm publish`.

## Running unit tests

Run `ng test custom-datepicker` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).
npm package: @pracht/adapter-cloudflare
Description: Cloudflare Workers adapter for pracht. Handles requests in the Workers `fetch` event, serves static assets via `env.ASSETS`, and supports ISG revalidation through KV.
Latest version: 0.0.4

# @pracht/adapter-cloudflare

Cloudflare Workers adapter for pracht. Handles requests in the Workers `fetch` event, serves static assets via `env.ASSETS`, and supports ISG revalidation through KV.

## Install

```bash
npm install @pracht/adapter-cloudflare
```

## Usage

Select the Cloudflare adapter when scaffolding with `create-pracht`, or add it to an existing project:

```bash
npm create pracht@latest my-app  # choose Cloudflare
```

Deploy with:

```bash
pracht build && wrangler deploy
```

## Features

- Converts Cloudflare Worker requests to standard Web Requests
- Static asset serving via `env.ASSETS`
- KV-based ISG revalidation
- Execution context passing for Cloudflare-specific APIs
npm package: @pracht/adapter-node
Description: Node.js HTTP adapter for pracht. Converts Node `http` requests to Web Requests, serves static assets, and handles ISG revalidation.
Latest version: 0.1.2

# @pracht/adapter-node

Node.js HTTP adapter for pracht. Converts Node `http` requests to Web Requests, serves static assets, and handles ISG revalidation.

## Install

```bash
npm install @pracht/adapter-node
```

## Usage

After building with `pracht build`, start the production server:

```bash
node dist/server/server.js
```

## Features

- Converts Node.js HTTP requests to standard Web Requests
- Serves static files from `dist/client/`
- Loads the Vite manifest for asset injection
- Supports ISG time-window revalidation
npm package: @pracht/adapter-vercel
Description: Vercel adapter for pracht. Supports serverless and edge function deployment via the Build Output API v3.
Latest version: 0.0.4

# @pracht/adapter-vercel

Vercel adapter for pracht. Supports serverless and edge function deployment via the Build Output API v3.

## Install

```bash
npm install @pracht/adapter-vercel
```

## Usage

Select the Vercel adapter when scaffolding with `create-pracht`, or add it to an existing project:

```bash
npm create pracht@latest my-app  # choose Vercel
```

Deploy with:

```bash
pracht build && vercel deploy --prebuilt
```

## Features

- Build Output API v3 integration
- Serverless function support
- Edge function support
npm package: @pracht/cli
Description: Command-line tool for developing, building, validating, and scaffolding pracht apps.
Latest version: 1.1.1

# @pracht/cli

Command-line tool for developing, building, validating, and scaffolding pracht apps.

## Install

```bash
npm install @pracht/cli
```

## Commands

### `pracht dev`

Start the local development server with SSR and HMR.

### `pracht build`

Create a production build with client/server output and SSG/ISG prerendering.

For Node.js targets, run the built server with:

```bash
node dist/server/server.js
```

### `pracht verify`

Run fast framework-aware verification checks without paying for a full build or
test loop. Use `--changed` to focus on changed manifest-managed files and
`--json` for machine-readable output.

```bash
pracht verify
pracht verify --changed
pracht verify --json
```

### `pracht generate route`

Create a new route module. In manifest apps this also updates `src/routes.ts`.

```bash
pracht generate route --path /dashboard --render ssr --shell app --middleware auth
```

### `pracht generate shell`

Create a shell module and register it in the app manifest.

```bash
pracht generate shell --name app
```

### `pracht generate middleware`

Create a middleware module and register it in the app manifest.

```bash
pracht generate middleware --name auth
```

### `pracht generate api`

Create an API route under `src/api/`.

```bash
pracht generate api --path /health --methods GET,POST
```

### `pracht inspect`

Inspect the resolved app graph. Use `--json` for agent/tool consumption.

```bash
pracht inspect --json
pracht inspect routes --json
pracht inspect api --json
pracht inspect build --json
```

### `pracht doctor`

Validate the local app wiring across the whole project. Use `--json` for
machine-readable output.

```bash
pracht doctor
pracht doctor --json
```
npm package: @pracht/core
Description: Core routing, rendering, server/client runtime, and type utilities for pracht.
Latest version: 0.2.1

# @pracht/core

Core routing, rendering, server/client runtime, and type utilities for pracht.

## Install

```bash
npm install @pracht/core preact preact-render-to-string
```

## API

### Route Manifest

- `defineApp()` — define the application and its route tree
- `route()` — declare a route with path, component, loader, and rendering mode
- `group()` — group routes under a shared shell or middleware

Route modules may export the page as a function default export or as a named
`Component` export. Named exports such as `loader`, `head`, `ErrorBoundary`, and
`getStaticPaths` keep their special route-module behavior.

### Server

- `handlePrachtRequest()` — server renderer that produces full HTML with hydration markers
- `matchAppRoute()` — segment-based route matching

`handlePrachtRequest()` sanitizes unexpected 5xx errors by default so raw server
messages do not leak into SSR HTML or route-state JSON. Explicit
`PrachtHttpError` 4xx messages are preserved. Pass `debugErrors: true` to expose
raw details intentionally during debugging; `@pracht/core` does not infer this
from environment variables. Debug responses also attach `error.diagnostics`
metadata for the failure phase and matched framework files when available.

### Client

- `startApp()` — client-side hydration and runtime
- `useRouteData()` — access loader data inside a route component
- `useRevalidateRoute()` — trigger a revalidation of the current route's data
- `useSubmitAction()` — submit a form action programmatically
- `<Form>` — progressive enhancement form component

### Types

- `LoaderData<T>` — infer the return type of a loader
- `RouteComponentProps<T>` — props type for route components
- `LoaderArgs` — argument type passed to loaders and actions

## Rendering Modes

Each route can specify its rendering mode:

- `ssr` — server-rendered on every request
- `ssg` — pre-rendered at build time
- `isg` — pre-rendered with time-based revalidation
- `spa` — client-only route rendering with optional shell/loading HTML on first paint
npm package: @pracht/vite-plugin
Description: Vite integration for pracht. Handles virtual module generation, multi-environment builds, and SSG prerendering.
Latest version: 0.1.2

# @pracht/vite-plugin

Vite integration for pracht. Handles virtual module generation, multi-environment builds, and SSG prerendering.

## Install

```bash
npm install @pracht/vite-plugin
```

## Usage

```ts
// vite.config.ts
import { defineConfig } from "vite";
import pracht from "@pracht/vite-plugin";

export default defineConfig({
  plugins: [pracht()],
});
```

## What It Does

- Generates virtual modules (`virtual:pracht/client`, `virtual:pracht/server`) from your route manifest
- Builds client and SSR bundles via Vite's multi-environment mode
- Pre-renders SSG and ISG routes at build time
- Provides HMR during development

## Peer Dependencies

- `vite@^8.0.0`
- `@cloudflare/vite-plugin@^1.0.0` (optional, for Cloudflare targets)
- `wrangler@^4.81.0` (optional, for Cloudflare targets)