Hello,
My team could use some clarification regarding the correct usage of @esri/calcite-components-react.
The Usage section of the framework integration docs states,
"The package includes the compatible version of the web component library as a dependency, so no need to install @esri/calcite-components separately.
However, the linked React example clearly references the calcite-components CDN and states that the custom elements need to be imported and defined on the browser.
This appears to be conflicting advice and it has led to team members using both patterns in our project. For what it's worth, both approaches seem to work, but we would like to drop the local copy of @esri/calcite-components if it's redundant.
Thank you
