Publish @opensysml/client to npm (first client-node release)

[someshSandbox]

Could @opensysml/client get its first npm release?

The release path looks complete, but it has never run:

• .circleci/config.yml has the release-node workflow and the publish-npm job. They build the five platform binaries, check the digests, and publish the platform packages and then the client, on a client-node-v<version> tag.
• client/node/package.json is 0.1.0, with @opensysml/sysml-grpc-* 0.1.0 as optional dependencies.
• No client-node-v* tag exists, and the registry has none of the packages:

$ npm view @opensysml/client version
npm error 404 '@opensysml/client@*' is not in this registry.
$ curl -s -o /dev/null -w '%{http_code}\n' https://registry.npmjs.org/@opensysml%2fsysml-grpc-darwin-arm64
404

The Python client for the same service is on PyPI (opensysml 0.9.0, released with v0.9.0), and the README's install line still says "once the first release is published".

Without a release, a Node consumer builds client/node from a checkout and imports dist/node/index.js by path. It also has to supply its own sysml-grpc, since the platform packages that would provide one aren't installable. With 0.1.0 on npm, npm install @opensysml/client gives the client and the right binary through optionalDependencies.

If something blocks the tag (for example the npm context, the org scope or the automation token), a note here on what's missing would help us plan around it.

[HuiJun]

Sure thing. Really the only reason it hasn't yet is because of the pile of things to do and no one has asked for it yet specifically. I'll add this to 0.9.1.

[someshSandbox]

Thanks :)