@ifc-lite/codegen 1.15.4 → 1.15.5

package/README.md

@@ -14,19 +14,25 @@ npm install --save-dev @ifc-lite/codegen
 
 ```bash
 # IFC4 (776 entities)
-npx ifc-lite-codegen ./schemas/IFC4.exp --out ./src/generated
+node dist/cli.js schemas/IFC4_ADD2_TC1.exp --output ./generated/ifc4
 
 # IFC4X3 (876 entities, includes infrastructure: roads, bridges, alignments)
-npx ifc-lite-codegen ./schemas/IFC4X3.exp --out ./src/generated
+node dist/cli.js schemas/IFC4X3.exp --output ./generated/ifc4x3
 ```
 
-Generated files (one per output directory):
+Pass `--rust` to also emit Rust type tables (consumed by the ifc-lite Rust core).
 
-```
-src/generated/
+Generated files (one per output directory, e.g. `./generated/ifc4`):
+
+```text
+generated/ifc4/
 ├── entities.ts          ← TypeScript interfaces for every entity
+├── types.ts             ← defined-type aliases
+├── enums.ts             ← enum definitions
+├── selects.ts           ← SELECT union types
 ├── schema-registry.ts   ← runtime metadata (parent, attributes, ...)
-├── types.ts             ← enum unions and SELECT types
+├── type-ids.ts          ← numeric type-id lookup tables
+├── serializers.ts       ← STEP serializer bound to the schema registry
 └── index.ts             ← barrel export
 ```
 
@@ -34,19 +40,16 @@ src/generated/
 
 ```typescript
 import { parseExpressSchema, generateTypeScript } from '@ifc-lite/codegen';
-import { writeFile } from 'node:fs/promises';
+import { readFile, writeFile } from 'node:fs/promises';
 
-const schema = parseExpressSchema('./schemas/IFC4.exp');
+const schema = parseExpressSchema(await readFile('./schemas/IFC4.exp', 'utf-8'));
 
 console.log(`Parsed ${schema.entities.length} entities, ${schema.types.length} types`);
 
-const generated = generateTypeScript(schema, {
-  inheritanceChain: true,
-  emitEnums: true,
-});
+const generated = generateTypeScript(schema);
 
-await writeFile('./src/generated/entities.ts', generated.entities);
-await writeFile('./src/generated/schema-registry.ts', generated.schemaRegistry);
+await writeFile('./generated/ifc4/entities.ts', generated.entities);
+await writeFile('./generated/ifc4/schema-registry.ts', generated.schemaRegistry);
 ```
 
 ## What you get

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ifc-lite/codegen",
-  "version": "1.15.4",
+  "version": "1.15.5",
   "description": "TypeScript code generator from IFC EXPRESS schemas",
   "type": "module",
   "repository": {
@@ -16,17 +16,27 @@
     "codegen",
     "typescript"
   ],
-  "author": "",
-  "license": "MIT",
+  "author": "Louis True",
+  "license": "MPL-2.0",
   "dependencies": {
     "commander": "^15.0.0",
-    "@ifc-lite/data": "^2.1.0"
+    "@ifc-lite/data": "^2.5.1"
   },
   "devDependencies": {
-    "@types/node": "^25.9.3",
+    "@types/node": "^26.1.0",
     "typescript": "^6.0.3",
-    "vitest": "^4.1.0"
+    "vitest": "^4.1.9"
   },
+  "publishConfig": {
+    "access": "public"
+  },
+  "homepage": "https://ltplus-ag.github.io/ifc-lite/",
+  "bugs": "https://github.com/LTplus-AG/ifc-lite/issues",
+  "files": [
+    "dist",
+    "schemas",
+    "README.md"
+  ],
   "scripts": {
     "build": "pnpm exec tsc",
     "dev": "pnpm exec tsc --watch",

package/.turbo/turbo-build.log

@@ -1,4 +0,0 @@
-
-> @ifc-lite/codegen@1.15.4 build /home/runner/work/ifc-lite/ifc-lite/packages/codegen
-> pnpm exec tsc
-

package/CHANGELOG.md

@@ -1,165 +0,0 @@
-# @ifc-lite/codegen
-
-## 1.15.4
-
-### Patch Changes
-
-- [#1151](https://github.com/LTplus-AG/ifc-lite/pull/1151) [`bfd9004`](https://github.com/LTplus-AG/ifc-lite/commit/bfd9004daa17f481a7b33b5c3c11f620e6cd894d) Thanks [@louistrue](https://github.com/louistrue)! - De-duplicate the STEP serializer into a single source of truth. The
-  schema-agnostic STEP serialization logic (`serializeValue`, `generateHeader`,
-  `parseStepValue`, `ref`/`enumVal`/`isEntityRef`/`isEnumValue`, and the
-  registry-injected `toStepLineWithRegistry` / `generateStepFileWithRegistry`)
-  previously existed as four hand-synced copies — the codegen template plus three
-  generated `serializers.ts` files — which had already silently drifted (the
-  runtime copy carried a `?? []` hardening the template lacked). It now lives once
-  in `@ifc-lite/data`; the per-schema bundles (parser runtime + codegen outputs)
-  are thin re-exports that only bind their own `SCHEMA_REGISTRY` to the
-  registry-coupled helpers, so the copies can never diverge again. A codegen test
-  asserts the generated bundle stays a thin re-export rather than re-inlining
-  logic.
-
-  Also fixes the broken `generate:ifc4` script (it pointed at a non-existent
-  `schemas/IFC4.exp`; the real file is `schemas/IFC4_ADD2_TC1.exp`). No public
-  behaviour change: `@ifc-lite/parser` re-exports the same serializer symbols as
-  before; `@ifc-lite/data` gains the shared primitives; `@ifc-lite/codegen` now
-  declares `@ifc-lite/data` as a dependency since the generated bundle imports it.
-
-- [#1143](https://github.com/LTplus-AG/ifc-lite/pull/1143) [`248f2c0`](https://github.com/LTplus-AG/ifc-lite/commit/248f2c09a4d61fa27dfeaba5511a2a641d4cd278) Thanks [@louistrue](https://github.com/louistrue)! - Preserve source IFC HEADER fields on round-trip export. Re-exporting an
-  imported file previously regenerated a fresh ifc-lite header, silently dropping
-  the source `FILE_DESCRIPTION` items (any `ViewDefinition [...]` label and vendor
-  identifier / coordinate-reference strings) and flattening the exact
-  `FILE_SCHEMA` token (e.g. `IFC4X3_ADD2` → `IFC4X3`, which some toolchains
-  reject).
-
-  The parser now captures the verbatim HEADER onto a new
-  `IfcDataStore.sourceHeader` (`IfcSourceHeader`, exported from `@ifc-lite/data`;
-  parser also exports `parseSourceHeader`), threaded through the worker transport.
-  `StepExporter` reproduces the source `FILE_DESCRIPTION` items and the exact
-  `FILE_SCHEMA` token when not converting schemas, falling back to parsing the
-  source bytes for cache-restored stores. Provenance stays honest:
-  `preprocessor_version` is set to `ifc-lite` while the source authoring tool is
-  kept as `originating_system`, and when mutations exist exactly one
-  `Re-exported by ifc-lite, N modification(s)` item is appended without removing
-  the source items. `generateHeader` now accepts description/author/organization
-  arrays plus a free-form schema token and STEP-escapes all fields; it also emits
-  a properly parenthesised `FILE_DESCRIPTION` list (the prior single-string form
-  was malformed STEP). Created-from-scratch (`IfcCreator`) and federated/merged
-  exports are unaffected — they keep their own provenance headers by design.
-
-- Updated dependencies [[`bfd9004`](https://github.com/LTplus-AG/ifc-lite/commit/bfd9004daa17f481a7b33b5c3c11f620e6cd894d), [`248f2c0`](https://github.com/LTplus-AG/ifc-lite/commit/248f2c09a4d61fa27dfeaba5511a2a641d4cd278), [`ddae2b0`](https://github.com/LTplus-AG/ifc-lite/commit/ddae2b0024f071d00f9e6e4b77e0be3965412ec3)]:
-  - @ifc-lite/data@2.1.0
-
-## 1.15.3
-
-### Patch Changes
-
-- [#946](https://github.com/LTplus-AG/ifc-lite/pull/946) [`6378998`](https://github.com/LTplus-AG/ifc-lite/commit/6378998ec146f7f9297ef5fcc5953b155fd6b5e0) Thanks [@louistrue](https://github.com/louistrue)! - Fix a batch of verified findings from a full-codebase review (security, correctness,
-  data-loss, and resource/memory leaks). Highlights:
-
-  **Security**
-
-  - collab-server: a malformed WebSocket frame no longer crashes the whole process
-    (decode is wrapped; a bad frame is rejected/audited instead of throwing).
-  - mcp: the local HTTP transport now validates `Host`/`Origin` and no longer sends a
-    wildcard `Access-Control-Allow-Origin`, closing a DNS-rebinding/CSRF hole; the
-    `AuthScope.modelIds` allowlist is now enforced at model resolution.
-  - server-bin: `extractZip` uses `execFileSync` (argv, no shell), removing command
-    injection via archive/destination paths.
-  - export / sdk / cli / mcp / lists / viewer CSV exporters now neutralize spreadsheet
-    formula injection (CWE-1236) consistently.
-  - create-ifc-lite: validates the project name (no path traversal) and drops the
-    unused `execSync`-based downloader.
-  - embed-sdk: inbound `postMessage` now validates `event.origin`.
-
-  **Correctness / data-loss**
-
-  - parser: `lengthUnitScale` survives the worker transport; the nested STEP list
-    parser is string-aware (commas/parens inside quoted values no longer mis-split).
-  - mutations: deleting a property from a session-created pset and replaying
-    `UPDATE_ATTRIBUTE` / `CREATE_PROPERTY_SET` mutations now work.
-  - export: merged-export ID remapping no longer rewrites `#N` inside quoted strings.
-  - drawing-2d: GPU section cutter triangle upload/readback use correct WGSL std-layout
-    offsets and strides.
-  - ifcx: cyclic children no longer abort the parse; spatial children round-trip; the
-    mesh transform guards a zero/non-finite homogeneous `w`.
-  - data / cache: a `NULL` string property value stays `null` instead of becoming `""`.
-  - pointcloud, bcf, server-client, query, viewer-core, viewer store/federation: assorted
-    decoding, federation-id, and selection-state fixes.
-
-  **Resource / memory leaks**
-
-  - geometry, query (DuckDB), renderer (GPU buffers), collab (federation presence),
-    sandbox (host log capture + runtime), mcp (clash mesh cache), server-bin (signal
-    listeners), and the viewer renderer on unmount now release resources deterministically.
-
-  **Hardening (apps, not published)**
-
-  - server: a dedicated `server-release` Cargo profile (`panic = "unwind"`) plus a
-    `CatchPanicLayer` contain a malformed-IFC parse panic to the offending request
-    instead of aborting the whole server.
-  - desktop (Tauri): a Content-Security-Policy is set, and unused `shell:*` /
-    `fs:allow-write|mkdir|remove` capabilities (and the unused shell plugin) are removed.
-
-  **Second pass** (additional verified findings)
-
-  - collab-server: S3 log load now follows `ListObjectsV2` pagination (no dropped frames);
-    awareness frames are size-capped + rate-limited; path-lock verify runs after role/rate-limit;
-    the blob route requires auth and `/metrics` can be token-gated.
-  - server-bin: downloaded binaries are SHA-256 verified against a release sidecar (fail-closed on
-    mismatch, warn-if-absent for older releases).
-  - extensions: inner-ring capability check fails _closed_ for unknown namespaces; signing
-    canonicalization is now injective (length-prefixed).
-  - correctness/leaks: mutations quantity type+unit preserved on replay; `findByProperty` boolean
-    comparisons; Parquet REAL columns kept as Float64; blob GC fail-safe on missing `uploadedAt`;
-    spatial-hierarchy + codegen cycle guards; BVH NaN edge; bSDD/playground caches bounded;
-    point-cloud GPU asset freed on federation error; mcp `parseColor` rejects non-hex; bcf/SVG/STEP
-    output escaping; and more.
-
-## 1.15.2
-
-### Patch Changes
-
-- [#494](https://github.com/louistrue/ifc-lite/pull/494) [`ec0d3a0`](https://github.com/louistrue/ifc-lite/commit/ec0d3a0e4c7f9eaeb26ab0a724fd76d955e52ac5) Thanks [@louistrue](https://github.com/louistrue)! - Remove recursive package `prebuild` hooks and run TypeScript via `pnpm exec` so workspace builds resolve correctly on Windows.
-
-## 1.15.1
-
-### Patch Changes
-
-- [#461](https://github.com/louistrue/ifc-lite/pull/461) [`6ce40dd`](https://github.com/louistrue/ifc-lite/commit/6ce40ddb0cace5f83c2438d2d4c4bd47703468f7) Thanks [@louistrue](https://github.com/louistrue)! - Clean up package build health for georeferencing work by fixing parser generation issues, making export tests resolve workspace packages reliably, removing build scripts that masked TypeScript failures, tightening workspace test/build scripts, productizing CLI LOD generation, centralizing IFC GUID utilities in encoding, and adding mutation test coverage for property editing flows.
-
-## 1.15.0
-
-### Minor Changes
-
-- [#354](https://github.com/louistrue/ifc-lite/pull/354) [`3f212f1`](https://github.com/louistrue/ifc-lite/commit/3f212f1e24b896cbc6ff63444c02635a1128ba3f) Thanks [@louistrue](https://github.com/louistrue)! - Replace hardcoded IFC schema with codegen from EXPRESS schema, adding full type entity support (776 entities)
-
-## 1.14.3
-
-## 1.14.2
-
-## 1.14.1
-
-## 1.14.0
-
-## 1.13.0
-
-## 1.12.0
-
-## 1.11.3
-
-## 1.11.1
-
-## 1.11.0
-
-## 1.10.0
-
-## 1.9.0
-
-## 1.8.0
-
-## 1.7.0
-
-## 1.2.1
-
-### Patch Changes
-
-- Version sync with @ifc-lite packages

package/INTEGRATION.md

@@ -1,360 +0,0 @@
-# Integration Guide: Using Generated IFC Types in Parser
-
-This guide explains how to integrate the generated TypeScript code from `@ifc-lite/codegen` into the `@ifc-lite/parser` package.
-
-## Overview
-
-The codegen package generates 5 TypeScript files from IFC EXPRESS schemas:
-
-1. **entities.ts** - Entity interfaces (776 for IFC4, 876 for IFC4X3)
-2. **types.ts** - Type aliases (397 for IFC4, 436 for IFC4X3)
-3. **enums.ts** - Enum definitions (207 for IFC4, 243 for IFC4X3)
-4. **selects.ts** - Union types (60 for IFC4, 61 for IFC4X3)
-5. **schema-registry.ts** - Runtime metadata (1.6 MB for IFC4)
-
-Total: ~75K lines of TypeScript covering 100% of the IFC schema.
-
-## Benefits
-
-### Before (Manual Implementation)
-- ~70 manually implemented entity types
-- ~7% schema coverage
-- Manual updates for new IFC versions
-- No materials, georeferencing, infrastructure
-
-### After (Code Generation)
-- 776-876 automatically generated entity types
-- 100% schema coverage
-- Automatic updates (regenerate from .exp files)
-- Full support: materials, georeferencing, roads, bridges, railways
-
-## Integration Steps
-
-### Step 1: Generate Code
-
-```bash
-cd packages/codegen
-
-# Generate IFC4 types
-npm run generate:ifc4
-
-# Generate IFC4X3 types (infrastructure support)
-npm run generate:ifc4x3
-```
-
-Generated files: `packages/codegen/generated/ifc4/` or `generated/ifc4x3/`
-
-> **Runtime dependency:** the generated `serializers.ts` is a thin re-export of
-> the schema-agnostic STEP serializer in `@ifc-lite/data` (it only binds the
-> bundle's `SCHEMA_REGISTRY`). Any project that consumes a generated bundle must
-> therefore have `@ifc-lite/data` installed. This keeps the serialization logic
-> in one place so the per-schema copies can never drift.
-
-### Step 2: Copy Generated Files to Parser
-
-Option A: **Direct Copy** (recommended for testing)
-
-```bash
-# Copy IFC4 generated types to parser
-cp -r packages/codegen/generated/ifc4/* packages/parser/src/schema/
-
-# Or IFC4X3
-cp -r packages/codegen/generated/ifc4x3/* packages/parser/src/schema/
-```
-
-Option B: **Symlink** (for development)
-
-```bash
-ln -s ../../codegen/generated/ifc4 packages/parser/src/schema
-```
-
-Option C: **npm Package** (for production)
-
-Publish `@ifc-lite/ifc4-schema` and import it:
-
-```typescript
-import { IfcWall, IfcDoor, SCHEMA_REGISTRY } from '@ifc-lite/ifc4-schema';
-```
-
-### Step 3: Update Parser Imports
-
-Replace the manual `ifc-schema.ts` with generated types:
-
-**Before:**
-```typescript
-// packages/parser/src/ifc-schema.ts
-export const IFC_SCHEMA = {
-  IfcWall: {
-    parent: 'IfcBuildingElement',
-    attributes: ['GlobalId', 'Name', ...],
-  },
-  // ... only ~70 entities
-};
-```
-
-**After:**
-```typescript
-// Use generated schema registry
-export { SCHEMA_REGISTRY, getEntityMetadata, getAllAttributesForEntity } from './schema/schema-registry';
-
-// Use generated types
-export type { IfcWall, IfcDoor, IfcWindow, IfcProject } from './schema/entities';
-export { IfcWallTypeEnum, IfcDoorTypeEnum } from './schema/enums';
-```
-
-### Step 4: Update Entity Extractor
-
-The `entity-extractor.ts` can now use generated types:
-
-**Before:**
-```typescript
-// Manual type checking
-if (typeName === 'IfcWall' || typeName === 'IfcDoor') {
-  // handle building elements
-}
-```
-
-**After:**
-```typescript
-import { getEntityMetadata, isKnownEntity } from './schema/schema-registry';
-
-// Schema-driven parsing
-if (isKnownEntity(typeName)) {
-  const metadata = getEntityMetadata(typeName);
-  const attributes = metadata.allAttributes; // includes inherited!
-
-  // Parse all attributes dynamically
-  for (const attr of attributes) {
-    parseAttribute(entity, attr.name, attr.type, attr.optional);
-  }
-}
-```
-
-### Step 5: Add Specialized Extractors
-
-With 100% schema coverage, you can now add extractors for previously missing concepts:
-
-#### Materials Extractor
-
-```typescript
-// packages/parser/src/material-extractor.ts
-import type { IfcMaterial, IfcMaterialLayer, IfcMaterialLayerSet } from './schema/entities';
-
-export function extractMaterials(entities: Map<number, IfcEntity>): Material[] {
-  // Now you have full type definitions for:
-  // - IfcMaterial
-  // - IfcMaterialLayer
-  // - IfcMaterialLayerSet
-  // - IfcMaterialProfile
-  // - IfcMaterialConstituent
-}
-```
-
-#### Georeferencing Extractor
-
-```typescript
-// packages/parser/src/georef-extractor.ts
-import type { IfcMapConversion, IfcProjectedCRS } from './schema/entities';
-
-export function extractGeoreferencing(project: IfcProject): GeoreferenceInfo {
-  // Parse IfcMapConversion and IfcProjectedCRS
-  // Transform coordinates to target CRS
-}
-```
-
-#### Infrastructure Support (IFC4X3)
-
-```typescript
-// packages/parser/src/infrastructure-extractor.ts
-import type { IfcRoad, IfcBridge, IfcRailway, IfcAlignment } from './schema/entities';
-
-export function extractInfrastructure(entities: Map<number, IfcEntity>) {
-  // Support for civil infrastructure:
-  // - Roads, bridges, railways, tunnels
-  // - Alignments and curve segments
-  // - Earthworks
-}
-```
-
-### Step 6: Update Tests
-
-Update parser tests to use generated types:
-
-```typescript
-import { IfcWall, IfcDoor } from './schema/entities';
-import { SCHEMA_REGISTRY } from './schema/schema-registry';
-
-describe('Entity parsing', () => {
-  it('should parse IfcWall with all attributes', () => {
-    const metadata = SCHEMA_REGISTRY.entities.IfcWall;
-
-    expect(metadata.parent).toBe('IfcBuildingElement');
-    expect(metadata.attributes).toHaveLength(1);
-    expect(metadata.allAttributes).toHaveLength(14); // Including inherited!
-  });
-});
-```
-
-## Usage Examples
-
-### Type-Safe Entity Access
-
-```typescript
-import type { IfcWall, IfcDoor, IfcWindow } from './schema/entities';
-import { IfcWallTypeEnum } from './schema/enums';
-
-// Type-safe entity access
-const wall: IfcWall = {
-  GlobalId: '2X3v_TggD0W8N...',
-  Name: 'Exterior Wall',
-  ObjectType: 'External',
-  PredefinedType: IfcWallTypeEnum.SOLIDWALL,
-  // TypeScript ensures all required fields are present!
-};
-
-// Autocomplete for attributes
-console.log(wall.PredefinedType); // TypeScript knows this exists
-```
-
-### Schema-Driven Parsing
-
-```typescript
-import { getEntityMetadata, getAllAttributesForEntity } from './schema/schema-registry';
-
-// Get metadata for any entity
-const wallMeta = getEntityMetadata('IfcWall');
-
-console.log(wallMeta.parent); // 'IfcBuildingElement'
-console.log(wallMeta.attributes); // Own attributes
-console.log(wallMeta.allAttributes); // Including inherited
-console.log(wallMeta.inheritanceChain); // ['IfcRoot', 'IfcObject', ...]
-
-// Parse attributes dynamically
-for (const attr of wallMeta.allAttributes) {
-  if (attr.optional) {
-    // Handle optional attribute
-  }
-  if (attr.isList) {
-    // Handle list/array
-  }
-}
-```
-
-### Inheritance Navigation
-
-```typescript
-import { getInheritanceChainForEntity } from './schema/schema-registry';
-
-// Get full inheritance chain
-const chain = getInheritanceChainForEntity('IfcWall');
-// ['IfcRoot', 'IfcObjectDefinition', 'IfcObject', 'IfcProduct',
-//  'IfcElement', 'IfcBuildingElement', 'IfcWall']
-
-// Walk up the chain to get parent attributes
-```
-
-## Performance Considerations
-
-### Bundle Size
-
-| Component | Size | Notes |
-|-----------|------|-------|
-| entities.ts | 149 KB | Entity interfaces |
-| types.ts | 61 KB | Type aliases |
-| enums.ts | 65 KB | Enum definitions |
-| selects.ts | 8 KB | Union types |
-| schema-registry.ts | 1.6 MB | Runtime metadata |
-| **Total** | **~1.9 MB** | Uncompressed |
-
-**Mitigation:**
-- Tree-shaking removes unused entities
-- gzip compression: ~1.9 MB → ~200 KB
-- Lazy load schema-registry only when needed
-- Split by IFC version (load IFC4 OR IFC4X3, not both)
-
-### Parse Performance
-
-Generated code has **minimal performance impact**:
-- Entity extraction remains byte-level scanning (fast)
-- Schema lookups are O(1) (hash maps)
-- No regex compilation overhead
-- Columnar storage unchanged
-
-Benchmark: Parsing a 50 MB IFC file
-- Before: ~2.5s
-- After: ~2.6s (4% slower, but 100% coverage vs 7%)
-
-## Migration Checklist
-
-- [ ] Generate types from IFC4 schema
-- [ ] Copy generated files to parser/src/schema/
-- [ ] Update imports in entity-extractor.ts
-- [ ] Replace manual ifc-schema.ts with SCHEMA_REGISTRY
-- [ ] Update property-extractor.ts to use schema metadata
-- [ ] Add material-extractor.ts (now possible!)
-- [ ] Add georef-extractor.ts (now possible!)
-- [ ] Update tests to use generated types
-- [ ] Run full test suite
-- [ ] Test with real IFC files
-- [ ] Measure bundle size impact
-- [ ] Optimize with tree-shaking if needed
-
-## Regenerating Types
-
-When IFC schemas are updated:
-
-```bash
-# Download new schema from buildingSMART
-curl -o packages/codegen/schemas/IFC4_ADD3.exp https://...
-
-# Regenerate types
-cd packages/codegen
-npm run generate -- schemas/IFC4_ADD3.exp -o generated/ifc4_add3
-
-# Copy to parser
-cp -r generated/ifc4_add3/* ../parser/src/schema/
-
-# Test
-cd ../parser
-npm test
-```
-
-## Troubleshooting
-
-### "Cannot find name 'IfcXxx'"
-
-**Solution:** Import from the correct file:
-```typescript
-import type { IfcWall } from './schema/entities'; // Entity
-import { IfcWallTypeEnum } from './schema/enums'; // Enum
-import type { IfcLabel } from './schema/types'; // Type alias
-```
-
-### "Type 'X' is not assignable to type 'Y'"
-
-**Solution:** The generated types are strict. Use type assertions carefully:
-```typescript
-const type = entity.attributes[0] as IfcLabel;
-```
-
-### Bundle size too large
-
-**Solution:**
-1. Enable tree-shaking in your bundler
-2. Lazy load schema-registry:
-```typescript
-const { SCHEMA_REGISTRY } = await import('./schema/schema-registry');
-```
-3. Split by IFC version (don't load both IFC4 and IFC4X3)
-
-## Next Steps
-
-1. **Test extensively** with real IFC files
-2. **Benchmark** performance impact
-3. **Implement specialized extractors** (materials, georeferencing)
-4. **Consider infrastructure support** (IFC4X3 for roads, bridges)
-5. **Optimize bundle size** if needed
-
-## Questions?
-
-See the main README in `packages/codegen/README.md` for more details.