npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@oxc-angular/vite

v0.0.38

Published

Oxc Angular Compiler Vite plugin

Readme

OXC Angular Compiler

A high-performance, Rust-based Angular compiler for Node.js. Provides both a standalone transformer and a Vite plugin for Angular applications.

Features

  • Fast compilation - Rust-based implementation via NAPI-RS
  • Vite integration - Full-featured Vite plugin with HMR support
  • Template compilation - Angular template to JavaScript transformation
  • Style encapsulation - ViewEncapsulation.Emulated support
  • Cross-file elision - Type-only import detection and removal
  • Drop-in replacement - Compatible API with @angular/compiler-cli

Installation

npm install @oxc-angular/vite
# or
pnpm add @oxc-angular/vite

Quick Start

Vite Plugin

// vite.config.ts
import { defineConfig } from 'vite'
import { angular } from '@oxc-angular/vite/vite-plugin'

export default defineConfig({
  plugins: [
    angular({
      tsconfig: './tsconfig.json',
      sourceMap: true,
    }),
  ],
})

Standalone Transformer

import {
  transformAngularFile,
  compileTemplateSync,
  extractComponentUrlsSync,
} from '@oxc-angular/vite'

// Transform an entire Angular file
const result = await transformAngularFile(sourceCode, 'app.component.ts', {
  sourcemap: true,
})

// Compile a template only
const template = compileTemplateSync('<div>{{ title }}</div>', 'AppComponent', 'app.component.ts')

API Reference

Package Exports

| Export | Description | | ----------------------- | ------------- | | @oxc-angular/vite | Vite plugin | | @oxc-angular/vite/api | Low level API |

Core Functions

Template Compilation

// Asynchronous
compileTemplate(
  template: string,
  componentName: string,
  filePath: string,
  options?: TemplateCompileOptions
): Promise<TemplateCompileResult>

Full File Transformation

transformAngularFile(
  source: string,
  filename: string,
  options?: TransformOptions,
  resolvedResources?: ResolvedResources
): Promise<TransformResult>

Component Metadata Extraction

// Extract templateUrl and styleUrls
extractComponentUrlsSync(
  source: string,
  filename: string
): ComponentUrls[]

Style Processing

// Apply ViewEncapsulation.Emulated
encapsulateStyle(
  css: string,
  componentId: string
): string

HMR Support

// Generate HMR update module
generateHmrModule(
  componentId: string,
  templateJs: string,
  styles: string[],
  declarationsJs: string,
  constsJs: string
): string
HMR + reload behavior matrix

The Vite plugin's handleHotUpdate hook dispatches every file change into one of these branches, mirroring Angular CLI's official behavior (@angular/build esbuild dev server):

| File | Change | Action | | -------------------------------------------------------------------- | ----------------------------------------- | ----------------------------------------- | | External .html (templateUrl) | any | angular:component-update HMR, no reload | | External .css/.scss/.sass/.less (styleUrl) | any | angular:component-update HMR, no reload | | Component .ts | inline template only | angular:component-update HMR, no reload | | Component .ts | inline styles: [...] only | angular:component-update HMR, no reload | | Component .ts | both inline template and styles | angular:component-update HMR, no reload | | Component .ts | class body / imports / decorator metadata | full reload | | Non-component .ts (utils, services, constants, lazy *.routes.ts) | any | full reload | | Global stylesheet (no styleUrl owner) | any | Vite default style HMR | | Anything in node_modules/ or *.spec.ts | any | ignore |

Set liveReload: false to disable both HMR and reloads — the plugin returns from handleHotUpdate without sending any event.

"No reload" means no reload is requested. Vite full-reloads any changed .html whose module list is empty or holds no js module, so the plugin registers each component template in the module graph (addWatchFile) and returns it as its own HMR boundary. Without that, Vite puts a full-reload on the socket on top of every template edit. Its client usually drops that payload because the path does not match location.pathname — but in middlewareMode the path is *, which always reloads (#443).

index.html is not a component template, so it still triggers a full reload.

Transform Options

interface TransformOptions {
  // Output
  sourcemap?: boolean

  // Compilation mode
  jit?: boolean
  hmr?: boolean
  advancedOptimizations?: boolean
  useDomOnlyMode?: boolean

  // i18n
  i18nUseExternalIds?: boolean

  // Final component style output
  minifyComponentStyles?: boolean

  // Component metadata
  selector?: string
  standalone?: boolean
  encapsulation?: 'Emulated' | 'None' | 'ShadowDom'
  changeDetection?: 'Default' | 'OnPush'
  preserveWhitespaces?: boolean

  // Cross-file elision
  crossFileElision?: boolean
  baseDir?: string
  tsconfigPath?: string
}

Vite Plugin Options

interface AngularPluginOptions {
  // Project configuration
  tsconfig?: string
  workspaceRoot?: string

  // File filtering
  include?: string | string[]
  exclude?: string | string[]

  // Features
  sourcemap?: boolean
  hmr?: boolean
  jit?: boolean
  advancedOptimizations?: boolean
  useDomOnlyMode?: boolean
  zoneless?: boolean
  liveReload?: boolean

  // Style processing
  inlineStylesExtension?: string
  minifyComponentStyles?: boolean | 'auto'

  // File replacements
  fileReplacements?: Array<{
    replace: string
    with: string
  }>
}

minifyComponentStyles resolves like this:

  • true: always minify component styles
  • false: never minify component styles
  • "auto" or undefined: follow the resolved Vite minification settings

For "auto", the plugin uses build.cssMinify when it is set, otherwise it falls back to build.minify. In dev, "auto" defaults to false.

Library builds (.d.ts)

For publishing an Angular library (the ng-packagr-style workflow, e.g. with Rolldown/tsdown), set compilationMode: 'partial'. This emits partial declarations (ɵɵngDeclareComponent, …) in the JavaScript output, and the plugin also augments the emitted .d.ts with Angular's Ivy type declarations (static ɵfac, static ɵcmp, …) so downstream consumers get full template type-checking against your library.

// vite.config.ts — Angular library build
import { angular } from '@oxc-angular/vite'
import dts from 'rolldown-plugin-dts' // or vite-plugin-dts / tsdown

export default defineConfig({
  plugins: [angular({ compilationMode: 'partial' }), dts()],
  build: { lib: { entry: 'src/public-api.ts', formats: ['es'] } },
})

The plugin does not generate the base .d.ts itself — a declaration generator (rolldown-plugin-dts, vite-plugin-dts, tsdown, or tsc) must produce them. The Angular members are then spliced into those files during generateBundle. The injected members reference i0 (the @angular/core namespace), and the plugin adds import * as i0 from "@angular/core"; to any .d.ts it augments.

Vite Plugin Architecture

The Vite plugin consists of these sub-plugins:

  1. Transform Plugin - Transforms Angular TypeScript files
  2. HMR Plugin - Handles hot module replacement for templates and styles
  3. Styles Plugin - Processes and encapsulates component styles
  4. Dts Plugin - Augments library .d.ts with Ivy type declarations (partial mode)

HMR Routes

| Route | Description | | -------------------- | -------------------------------- | | /@ng/component/:id | Serves compiled template updates | | /@ng/styles/:id | Serves style updates |

Supported Angular Features

Templates

  • Control flow (@if, @for, @switch, @defer)
  • Property/attribute/class/style bindings
  • Event bindings and two-way binding
  • Template references and variables
  • Content projection (ng-content)
  • Structural directives

Components

  • Standalone components
  • Host bindings and listeners
  • Input/Output decorators
  • Query decorators (ViewChild, ContentChild, etc.)
  • View encapsulation modes
  • Change detection strategies

Styles

  • Inline styles
  • External styleUrls
  • ViewEncapsulation.Emulated
  • CSS attribute selector scoping

i18n

  • External message IDs
  • File-based naming

Platform Support

Pre-built binaries for:

| Platform | Architecture | | -------- | ----------------------- | | macOS | Apple Silicon (aarch64) | | macOS | Intel (x86_64) | | Windows | x86_64 | | Windows | aarch64 | | Linux | x86_64 (glibc) | | Linux | x86_64 (musl) | | Linux | aarch64 (glibc) | | Linux | aarch64 (musl) |

Requirements

  • Node.js 20.19.0+ or 22.12.0+
  • Vite 6.0.0+ (for Vite plugin)

Development

# Build native bindings
pnpm run build:native

# Build TypeScript
pnpm run build:ts

# Run tests
pnpm test

# Run E2E tests
pnpm run test:e2e

Build Features

| Feature | Description | | -------------------- | ----------------------------------- | | allocator | Use MiMalloc for better performance | | cross_file_elision | Enable cross-file import analysis |

# Build with all features
pnpm run build-dev --features allocator,cross_file_elision --release

Project Structure

napi/angular-compiler/
├── src/
│   └── lib.rs              # NAPI bindings (Rust)
├── core/                    # TypeScript utilities
│   ├── index.ts            # Main exports
│   ├── program.ts          # OxcNgtscProgram
│   ├── compiler.ts         # OxcAngularCompiler
│   └── config.ts           # Configuration reader
├── vite-plugin/            # Vite plugin
│   ├── index.ts            # Main plugin
│   ├── angular-jit-plugin.ts
│   └── angular-build-optimizer-plugin.ts
├── e2e/
│   └── compare/            # Comparison test runner
└── package.json

Related