Issue Category

Compilation Bug

Bug Description

While working on #812, I found a related compiler bug. TypeScript type arguments in class extends clauses are leaking into JavaScript output for .ripple files. For example, class StringMap extends Map<string, string> {} is emitted with <string, string> still present, which produces invalid JavaScript and causes a browser syntax error like Unexpected token '<'.

Reproduction Steps

1. Create a .ripple file with a class that uses type arguments in an extends clause:

export class StringMap extends Map<string, string> {
	constructor() {
		super();
	}
}

export component App() {
	const map = new StringMap();
	map.set('hello', 'world');
	<div>{map.get('hello')}</div>
}

2. Compile or run the file in the Ripple playground or in a Vite app using published ripple@0.3.3.
3. Inspect the generated client output.
4. Notice that the emitted JS still contains:export class StringMap extends Map<string, string> {
5. Open the app in the browser and observe the syntax error:
   Uncaught SyntaxError: Unexpected token '<'

Playground Repro

• https://www.ripple-ts.com/playground?v=0.3.3&title=Counter#config=code%2FN4IgLglmA2CmIC4QGED2BXAdmWAnEANCACawDOAxrhAA6SqaIiEgAWsAhsUwDwC2sMBwAEFVh1xlBAXgA6IAKoAVAGIBaABzzhAegB8szP0EjMHAXJAA3CLADuNVLjDaKDHNkt2IxMK2mkNhSwat6%2BrATCEJhQEBzQapTxsNIAjAB0AAza%2BiysYHzQAIJgYJJM0ByYAOaWsJiulWRklvIsQtVkiADaALpEHBSQVrAAosRQTkyU1HQsfBIA1ug0iKCVNegc1fBI%2BYUsbtj1YLwztGDCYACeNCnyfKjE6HDyBg2QfI7OwsDCj1hLgBfYQAM1wqD4wgA5LMaHBoQBuQyyT7fS4AKmEHDIwnOdDBEKh8nSOnxYHScNeIGRDUwwlEDDIl1gAA90bjpMIAPIAIwAVrAhulFrBrmQABTkgCUtIZR2ZwiKNBowi5bI56TgNT8aukXNSKJcYAA-HiqBduhqnGAyN1Mr1ekbUQhhFKLXR0qRQRwXpcAD7%2B82zCnK1WB4OW63OMjpUHRYgS2BqvRXW6wVCgyN0K29PVc6GgrBDCAMaHCaW9WWGBkQLMSm53TNKlXCACE%2BphRcwJbL0t%2BNYZV1YELswkw9mEo1wENwEuhADlUMIrPEfMJo5dQRhMMRodX6cIgYOAdgJWHIsBBwyhLgdmBXcRUBR0AJsOleU9rukOCr6sRkFYCBoETJ8XzfCkqE4HBRjgCD5wmKx92lAhByBA8eDJD0wD0EAgSIZlrjgNYQA2aoth2JgKGaQ53BOJg8h8UhMDQY5sCYT9iGuX4wXcNQfT4YDrldNRf3hEIyHFHA%2BEiAAhaBokWABZQYAGUpNgPgVHcSJoVU2BqlQZMFAASWhSIACVUE-MBUEiblWWuHZMEiBReUBdBImQKpb1gaBoF07k7npVSqjIcyYQACT8kZIAoEQF1gdBYAisgwsSPA60RYReUGRZqghLBiFdVgyGgCVMkiTIAFJIlSDRqtlRloCcV0AGJQU6o88II7CSLIijdhAKl4CII4PFOJBN1EJpcVUspomqFTVTZDxiFxZaeGZagakibbFtTK8PgVMp0CGJwJX7I7UVRMgVjwS7aVRY9MBe6a3C%2BBgThbGhLoHY6mUuBZVS5Ccx3mnalt-R6jWB9IpDAed2H81AIuhOwnBA-cnrAHhEL0YA4fvJG-Ja-cgUw-HDCBHqQEIuAyHYQQugQPpepDFm2ZAaiyAABVwchBAYogaAhYJmicTn%2Bm59BmUhfTSkWlnQBGkiRkkUtGCQTJ0gAZj1vD8JACBPpjNYjcbchzaIHBmWV0iqnI7Yhst8laLYybmCN9WyE1pgABYAHZ2lQVBoHt%2BoOF5OBuCQeJoBYQZhiGhUw9GumhDAWWqJaqRuCBIEgA

Repository:

• https://github.com/RazinShafayet2007/ripple-type-args-repro
  Run locally:
  git clone https://github.com/RazinShafayet2007/ripple-type-args-repro.git
  cd ripple-type-args-repro
  pnpm install
  pnpm check:compiled
  pnpm dev

Then:

• inspect the compiled output from pnpm check:compiled
• open the dev server in the browser
• observe the Unexpected token '<' error in the console

Environment

- OS: [Ubuntu 22.04.5 LTS]
- Browser: [Chrome 142.0.7444.134]
- Ripple Version: [0.3.3]
- Node Version: [22.17.1]

Additional Context

I found this while working on #812, which was another case of TypeScript-only class syntax leaking into emitted JavaScript for .ripple files. This looks like a related compiler emit bug, but for type arguments in class extends clauses instead of implements.

Checklist

• I've searched for existing issues
• I'm willing to help implement a fix