Publish @pascal-app/nodes to npm?

[archicorp46-debug]

Hi! We're building a web CAD product on top of @pascal-app/{core,viewer,editor}@0.9.1 (pinned) — thanks for the great engine.

@pascal-app/editor imports @pascal-app/nodes, but that package isn't published to npm, so embedders currently have to vendor it from the repo tag to get a working nodeRegistry (otherwise every node renders null). We're carrying a vendored copy of tag v0.9.1 mapped via tsconfig paths, which works but adds pin-upgrade friction.

Is publishing @pascal-app/nodes on the roadmap? Happy to help with whatever makes it easier (CI publish workflow PR, exports map, etc.). We'd drop our vendor copy the day it lands.

[Aymericr]

This is now available: #506 added @pascal-app/nodes to the release pipeline, and npm currently serves @pascal-app/nodes@0.1.1 (paired with @pascal-app/{core,viewer,editor}@0.9.2). Load it before mounting the viewer with await loadPlugin(builtinPlugin), importing loadPlugin from @pascal-app/core and builtinPlugin from @pascal-app/nodes. Thanks for surfacing the embedder friction.