@typespec/http-server-js@0.58.0-alpha.9

Features

• #5906 Implement basic project scaffolding.

@typespec/compiler@0.65.3

Bug Fixes

• #6041 Fix validation issue in @opExample when using versioning/mutators

@typespec/http-client@0.1.0

Efv2 to main (#5996)

# Efv2 Integration  

This PR introduces the work on **Emitter Framework v2** from the feature
branch into main. The existing emitter framework functionality remains
unchanged for now, the new framework is added as a new package
@typespec/emitter-framework

### **Core Changes**  

- **Compiler Alloy Support**  
- The compiler now detects if `$onEmit` returns an **Alloy component**.
If so, it loads Alloy and calls `render`.
  - This enables emitters to use Alloy components.  

- **New Package: `@typespec/emitter-framework`**  
- Wraps raw Alloy components to accept **TypeSpec types as props** and
automatically generate language elements.
- Currently includes a **subexport for TypeScript (`/typescript`)**,
with plans to extend support to other languages.
- Example: `ts.Interface` can take a `Model` or `Interface` and directly
render a TypeScript interface with model properties or operation
signatures.

- **New Package: `@typespec/http-client`**  
- Provides **TypeKits** for querying the **type graph** in the context
of an **HTTP client**.
- The goal is to eventually **power TCGC** and host decorators that make
sense in this context.
- Remains **decoupled from Azure**, but we may later introduce an
extension package (`@azure-tools/http-client-azure`) for Azure-specific
logic and decorators.

###  **Follow Up Work**  
- Deprecate EFv1
- A follow up API review and clean-up will be needed, specifically
around TypeKits

@typespec/emitter-framework@0.1.0

Efv2 to main (#5996)

# Efv2 Integration  

This PR introduces the work on **Emitter Framework v2** from the feature
branch into main. The existing emitter framework functionality remains
unchanged for now, the new framework is added as a new package
@typespec/emitter-framework

### **Core Changes**  

- **Compiler Alloy Support**  
- The compiler now detects if `$onEmit` returns an **Alloy component**.
If so, it loads Alloy and calls `render`.
  - This enables emitters to use Alloy components.  

- **New Package: `@typespec/emitter-framework`**  
- Wraps raw Alloy components to accept **TypeSpec types as props** and
automatically generate language elements.
- Currently includes a **subexport for TypeScript (`/typescript`)**,
with plans to extend support to other languages.
- Example: `ts.Interface` can take a `Model` or `Interface` and directly
render a TypeScript interface with model properties or operation
signatures.

- **New Package: `@typespec/http-client`**  
- Provides **TypeKits** for querying the **type graph** in the context
of an **HTTP client**.
- The goal is to eventually **power TCGC** and host decorators that make
sense in this context.
- Remains **decoupled from Azure**, but we may later introduce an
extension package (`@azure-tools/http-client-azure`) for Azure-specific
logic and decorators.

###  **Follow Up Work**  
- Deprecate EFv1
- A follow up API review and clean-up will be needed, specifically
around TypeKits

@typespec/compiler@0.65.2

Bug Fixes

• #6003 Fix regression where enum values would report not being assignable to their enum when using versioning

@typespec/http-server-javascript@0.58.0-alpha.9

Features

• #5906 Implement basic project scaffolding.

@typespec/compiler@0.65.1

Bug Fixes

• #5975 Downgrade arborist dependency which added node20+ requirement

typespec-vscode@0.64.1

Patch Changes

• #5620Enhance the UI experience for code generation

@typespec/http-server-csharp@0.58.0-alpha.8

Bug Fixes

• #5626 Fixes controller generation with incorrect return when NoContent is in the spec
• #5733 Add scaffolding option for csharp generator

Bump dependencies

• #5690 Upgrade dependencies

@typespec/rest@0.64.1

Bug Fixes

• #5726 Updates CollectionWithNextLink to support pagination