Closed arjanvanzutphen closed 10 months ago
@arjanvanzutphen There was a duplicate of this issue created that has reproduction instructions that shows the cause of this behavior. #8143
It looks like you have to make sure to import components from @esri/calcite-components
in addition to the react wrappers like the sample on that issue does to mitigate this issue.
Check existing issues
Actual Behavior
Calcite Components in React don't get completely loaded on the initial load. It's mostly icons that are directly not visible. After saving the right file (containing the components) in VS Code, the page gets refreshed and the application shows all components.
Before (behavior after a f5 refresh): After (behavior after saving the
App.jsx
in VS Code:Expected Behavior
All components are shown as they should on the initial load.
Reproduction Sample
https://github.com/arjanvanzutphen/ccr-initial-loading-issue
Reproduction Steps
npm install
andnpm run dev
Reproduction Version
1.9.1
Relevant Info
Edge (117), Chrome (116), Firefox (118)
Regression?
-
Priority impact
p3 - want for upcoming milestone
Impact
Missing components results in debugging activities where a 'save' of a certain file would suffice, but it's not always clear which file
Calcite package
Esri team
Professional Services - Services Delivery