@wwtelescope/embed 1.7.0

@wwtelescope/embed 1.7.0 (2023-09-15)

• Require the new, ESM-based version of the WebGL engine (#271, @pkgw). While
  the engine transition should not affect any packages that depend on it, such
  as this one, this requirement will help isolate any bugs associated with the
  transition.
• Update sponsorship branding and "front door" email address (#269, #271, @pkgw).

@wwtelescope/embed-creator 0.5.0

@wwtelescope/embed-creator 0.5.0 (2023-09-15)

• Require the new, ESM-based version of the WebGL engine (#271, @pkgw). While
  the engine transition should not affect any packages that depend on it, such
  as this one, this requirement will help isolate any bugs associated with the
  transition.
• Update sponsorship branding and "front door" email address (#269, #271, @pkgw).

@wwtelescope/embed-common 0.3.5

@wwtelescope/embed-common 0.3.5 (2023-09-15)

• Update sponsorship branding and "front door" email address (#269, #271, @pkgw).

@wwtelescope/astro 0.2.4

@wwtelescope/astro 0.2.4 (2023-09-15)

• Update sponsorship branding and "front door" email address (#269, #271, @pkgw).

@wwtelescope/engine 7.29.0

@wwtelescope/engine 7.29.0 (2023-09-14)

Historically, the WWT engine in this module has consisted of JavaScript code
that was transpiled from a C# codebase using an unmaintained tool called
ScriptSharp. In this release, we drop the C# and work directly from JavaScript
(#261, #262, @pkgw).

The intention is that this change should be invisible to consumers of this
module. However, a few internal APIs have been renamed as part of the
adaptation, to better isolate dependencies. It is possible that external code
referenced these symbols despite their internal nature, but since this is
unsupported and we are not aware of any actual instances of this, we are not
categorizing these as API breaks:

• Some APIs in the Planets module/class have been moved into a new
  Planets3d name
• RenderContext.useGl become render_globals.(set_)useGl
• RenderContext.useGlVersion2 become render_globals.(set_)useGlVersion2
• Tile.demEnabled become render_globals.(set_)tileDemEnabled
• Tile.prepDevice become render_globals.(set_)tilePrepDevice
• Tile.uvMultiple become render_globals.(set_)tileUvMultiple
• TileCache.accessID become render_globals.(set_)tileCacheAccessID
• TileCache.addTileToQueue become render_globals.(set_)tileCacheAddTileToQueue
• TileCache.getCachedTile become render_globals.(set_)tileCacheGetCachedTile
• TileCache.getTile become render_globals.(set_)tileCacheGetTile
• TileCache.removeFromQueue become render_globals.(set_)tileCacheRemoveFromQueue
• WWTControl.singleton.freestandingMode became data_globals.(set_)freestandingMode
• Object3d.maX_VERTICES and Object3d.maX_POLYGONS have disappeared.

It is also possible that the reorganization has unintentionally introduced
changes breaking existing code or behaviors, although a great deal of effort has
been spent to test that no visible changes have occurred. Any behavior changes
traceable to this migration are bugs that will be fixed.

The new codebase is written in plain JavaScript with ES6 ("ESM") module
syntax. Webpack then assembles the modularized source files into a UMD-style
single module file, the same form factor as delivered in previous releases. This
new approach will dramatically ease many aspects of WWT engine development
especially the use of JavaScript libraries and browser features, debugging, and
streamlining the build.

This release does not support building against the individual ESM module
files, although you might be able to get such a use case to work. This is an
obvious potential direction for future work. Another possible direction for work
is a port to TypeScript.

@wwtelescope/engine-pinia 0.8.0

@wwtelescope/engine-pinia 0.8.0 (2023-09-14)

• Add a customId prop the WWT component (#265, @nmearl). This allows you to
  precisely control the DOM id of the <div> that the app will bind to, in case
  the default ID selection (wwtcmpt${N}) does not work. In particular, if you
  have multiple independent WWT Vue apps within the same DOM tree, you can use
  this to avoid clashes.

@wwtelescope/research-app-messages 0.17.1

@wwtelescope/research-app-messages 0.17.1 (2023-07-23)

• Add a type: module field to the package.json file (#264, @pkgw). This more
  accurately reflects the files that we're distributing.

@wwtelescope/engine 7.28.2

@wwtelescope/engine 7.28.2 (2023-07-23)

• Actually use the crosshairs color setting (#260, @Carifio24).

@wwtelescope/engine-types 0.6.5

@wwtelescope/engine-types 0.6.5 (2023-07-23)

• Add a type: module field to the package.json file (#264, @pkgw). This more
  accurately reflects the files that we're distributing.

@wwtelescope/engine-helpers 0.15.1

@wwtelescope/engine-helpers 0.15.1 (2023-07-23)

• Add a type: module field to the package.json file (#264, @pkgw). This more
  accurately reflects the files that we're distributing.