Release issues on CDN and zero API documentation

GregoryBologna

I recently posted a research question to the github project. We had to change CDN references from unpgk.com to js.arcgis.com because the former no longer responds reliably and appears to have security vulnerability issues, as far as our security goes. During the change, we found that js.arcgis.com performs very well compared to unpkg.com, but the latest version (1.0.7) doesn't exist at js.arcgis.com. Seems strange to me that the latest build wouldn't be here? Additionally, why is the Esri Calcite API documentation so far behind?

Research question on github

https://github.com/Esri/calcite-components/issues/6492

KittyHurley

Hello @GregoryBologna,

You can certainly use the js.arcgis.com CDN if unpkg.com doesn't suit the organization's security or needs, which is also documented on the Getting started page.

The builds on js.arcgis.com can be seen with the following links (updated to 1.0.7) :

• JavaScript: https://js.arcgis.com/calcite-components/1.0.7/calcite.esm.js 
• CSS: https://js.arcgis.com/calcite-components/1.0.7/calcite.css

As for the documentation, our page releases weekly on Wednesday, and will update from 1.0.5 to 1.0.7. Since we are releasing patches with only bug fixes, the documentation is up-to-date.

Upcoming monthly and quarterly releases will still take place prior to documentation page updates, but will fall within the same week moving forward.