Aymeric RabotandClaude Opus 4.8
1b4c656901
Make the editor packages compatible with, and benefit from, the native Go
compiler (TypeScript 7 / tsgo) while keeping the npm publish path on stable tsc.
- Add @typescript/native-preview (pinned 7.0.0-dev.20260624.1). tsgo coexists
with typescript@6, which Next typegen and the IDE plugin still need until the
TS 7.1 programmatic API ships.
- Fix two react-three-fiber JSX augmentations the native checker rejects but
tsc tolerated:
- viewer: map only LineBasicNodeMaterial (the one webgpu node material used as
a JSX tag) instead of the whole three/webgpu namespace (TS2320/TS2590).
- plane-box-select-tool: drop the redundant `IntrinsicElements extends
ThreeElements` block — it duplicated R3F's global augmentation and, by
referencing @react-three/fiber's ThreeElements directly, hit a bun peer-dep
variant-directory duplicate under tsgo (TS2320). r3f.d.ts already covers
those JSX intrinsics. Types-only — no runtime change.
- check-types -> tsgo --noEmit (editor, @repo/ui, editor app, ifc-converter app)
- emit-package dev watch -> tsgo --build --watch
- build/publish stay tsc --build (prepublishOnly + release.yml unchanged;
emitted .d.ts is byte-identical to tsc output)
- bump next 16.2.6 -> 16.2.9
tsc remains the source of truth and fallback. Published artifacts unchanged.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
IFC → Pascal Converter
A web app that converts IFC building models into Pascal scene-graph JSON and
previews the result in the real @pascal-app/viewer. Drop in an .ifc file
(or pick a bundled example), inspect what was extracted, and download the
JSON to load into the Pascal editor.
⚠️ Early alpha
This converter is in early alpha. IFC is a sprawling, loosely-followed standard and real-world exports vary wildly — so expect rough edges: misplaced or missing elements, walls that default to a fixed height when their geometry can't be read, items skipped entirely, and element types that aren't mapped yet. The output is meant for previewing and iterating, not production.
Contributions very welcome — if you hit a file that converts badly, a sample IFC + a note on what's wrong is hugely helpful, and PRs improving the conversion (better geometry extraction, more element types, edge-case handling) are exactly what this needs. Jump in. 🙏
How it works
@pascal-app/ifc-converter(packages/ifc-converter) — the pure conversion logic. Parses IFC via web-ifc, maps elements onto Pascal node schemas from@pascal-app/core. No DOM, no React.- This app — the UI: drop zone, example picker, element search/filters, the 3D preview, and JSON download.
Develop
bun dev # from this directory, or `turbo run dev` at the repo root
The web-ifc.wasm binary is copied into public/ automatically on
install/dev/build (scripts/copy-web-ifc-wasm.mjs). Large example IFCs are
fetched from a public bucket at runtime; the small ones are committed under
public/test-ifc-files/. Override the bucket with
NEXT_PUBLIC_IFC_EXAMPLES_BASE_URL.
Known limitations (help wanted)
- Plain
IFCWALL(Brep/mapped geometry) falls back to a default height — exact per-wall heights need geometry-AABB extraction. - Items (furniture, etc.) are skipped — Pascal items require a catalog asset.
- Beams have no Pascal node type yet and are skipped.
- Doors/windows are matched to walls by proximity when the IFC omits fill relationships; matching isn't perfect.
- Stairs/roofs are placeholders (bounding box / flat polygon in metadata).