@pascal-app/nodes not published to npm + npm publish cadence

[MML-bath]

Hi — we're building on top of Pascal and loving it. Two things that would make our lives significantly easier:

1. @pascal-app/nodes is not published to npm.
We have to install it from a local clone of this repo, which means we need to keep the source on disk, run tsc --build manually before installing, and stay on top of git pull ourselves. Any chance of publishing it to npm alongside the other packages?

2. npm publish cadence.
The npm packages (core/viewer/editor) are currently at 0.9.1 published 15 days ago, but the GitHub main branch already has meaningful commits since then (GLB export fix, MEP movement controls, viewer fallback fixes etc). We end up having to install from local source anyway to get the latest fixes.

We're not asking for a specific release schedule — even a rough "we publish to npm after each significant batch of fixes" would help us know when it's safe to use npm vs local source.

Thanks for the great work on Pascal — the v0.9.1 preset system and building manipulation overhaul are exactly what we needed.

[Aymericr]

This is resolved for npm consumers. #506 added @pascal-app/nodes to the coordinated release workflow; the live versions are @pascal-app/nodes@0.1.1 and @pascal-app/{core,viewer,editor}@0.9.2. Install the aligned packages, then call await loadPlugin(builtinPlugin) before mounting (loadPlugin from core, builtinPlugin from nodes). We do not have a fixed public cadence to promise yet, but releases are now coordinated rather than leaving nodes out of the pipeline.

[Aymericr]

Update: @pascal-app/nodes is published now — npm view @pascal-app/nodes version returns 0.1.1. So the blocker in this thread is resolved; you can install it directly rather than vendoring from the repo.

Worth noting the version skew, since it will look odd otherwise: core, viewer, and editor are at 0.9.2 while nodes is at 0.1.1. nodes started its own version line when it was split out, so its number is younger — it is not a pre-release of the others and it is not behind them in content. Match nodes to whatever core version you're on by release date rather than by number.

Closing as resolved. If you hit an install or peer-dependency problem with it, open a fresh Q&A discussion — that's a different question from "is it published" and deserves its own thread.

[Aymericr]

Release follow-up for @MML-bath and anyone tracking the npm path: the August 18, 2026 coordinated beta is now published.

• @pascal-app/{core,viewer,editor,nodes,ifc-converter}@1.0.0-beta.5
• @pascal-app/mcp@1.0.0-beta.6
• @pascal-app/cli@1.0.0-beta.1

This batch includes the wall-runtime work from Andrei Efremov (@toycenterboss-bot), the configurable viewer frame cap from Steffen Oftedal (@Uxtopia), and the integrated runtime ownership and cleanup fixes. The release workflow smoke-tested the packed CLI and portable editor before publishing all packages together.

We still are not promising a fixed calendar cadence, but the practical policy remains significant coordinated batches, with nodes included in the same release train. Thanks again for raising the original packaging and cadence gap.