abstract class keyword not stripped from compiled output

[mikitahimpel]

Bug Description

When @oxc-angular/vite compiles a file with an abstract decorated class, the output retains the TypeScript abstract keyword, producing invalid JavaScript.

Reproduced in a minimal Vite + @oxc-angular/vite project (no Storybook, no Vitest).

Input (base.provider.ts):

import { Injectable } from '@angular/core';

@Injectable()
export abstract class BaseProvider {
    protected abstract get name(): string;
    protected abstract initialize(): void;

    public greet(): string {
        return `Hello from ${this.name}`;
    }
}

Build error:

let BaseProvider = abstract class BaseProvider {
                            ^ Expected a semicolon

Expected: The abstract keyword should be stripped. Abstract methods should also be stripped or replaced with empty stubs.

Environment

• @oxc-angular/vite: 0.0.17
• Vite: 8.0.0 (also reproduced with rolldown-vite 7.3.1)
• Angular: 20.x
• macOS (Apple Silicon)

[hyf0-agent]

I attempted to reproduce this but was unable to trigger the build error with a minimal setup.

Reproduction repo: https://github.com/hyf0-agent/oxc-angular-abstract-repro

The repo uses the exact input from the issue (@Injectable() on an abstract class with abstract methods) and the same dependency versions (@oxc-angular/vite@0.0.17, Vite 8.0.0, Angular 20.x).

Both vite build (Vite 8.0.0) and rolldown-vite build (7.3.1) succeed — the abstract keyword is correctly stripped from the final output by Vite/Rolldown's built-in TypeScript handling, which runs after the Angular plugin's order: "pre" transform.

The Angular compiler's transformAngularFile API does retain abstract in its output (it only handles Angular-specific transforms, not full TS→JS), but this is expected since downstream TS stripping takes care of it.

Could you share a reproduction repo? It's possible the issue is caused by another plugin in the pipeline or a specific tsconfig/build configuration.