V2 JSCAD Packages Available!

The V2 JSCAD project just took a huge step forward, as all V2 JSCAD packages have been published to NPM.
Successfully published:  @jscad/cli@2.0.0alpha.7  @jscad/core@2.0.0alpha.7  @jscad/amfdeserializer@2.0.0alpha.5  @jscad/amfserializer@2.0.0alpha.6  @jscad/dxfdeserializer@2.0.0alpha.5  @jscad/dxfserializer@2.0.0alpha.5  @jscad/ioutils@2.0.0alpha.5  @jscad/io@2.0.0alpha.6  @jscad/jsondeserializer@2.0.0alpha.5  @jscad/jsonserializer@2.0.0alpha.5  @jscad/objdeserializer@2.0.0alpha.5  @jscad/stldeserializer@2.0.0alpha.5  @jscad/stlserializer@2.0.0alpha.5  @jscad/svgdeserializer@2.0.0alpha.5  @jscad/svgserializer@2.0.0alpha.6  @jscad/x3dserializer@2.0.0alpha.6  @jscad/modeling@2.0.0alpha.5  @jscad/arrayutils@2.0.0alpha.2  @jscad/imgutils@2.0.0alpha.3  @jscad/reglrenderer@2.0.0alpha.7  @jscad/vtree@2.0.0alpha.6  @jscad/web@2.0.0alpha.9 lerna success published 22 packages
For those looking to grab these from NPM, there's some special setup required. The above packages have been published with the 'alpha' tag to NPM. These are 'alpha' releases and therefore projects need to specifically use this tag.
From the command line:
npm install @jscad/modeling@alpha
Inside NPM packages:
"dependencies": { "@jscad/modeling": "alpha" }

@BarbourSmith Thanks.
I noticed that as well. For now, you'll have to manually switch the version to 'alpha'.

These are FANTASTIC! I am already having great success using them.
I've noticed something a little bit strange, but I'm not sure if its a bug. When I run
npm install @jscad/modeling@alpha
I get a successful install, but the dependency added to the package.json file looks like:
"@jscad/modeling": "^2.0.0alpha.5",
Which ends up not working down the road when I run 'npm install' for the whole project.