webcomponents-react Date picker or date range picker not displayed into browser page when after hard reload chrome browser (used version 2.15.0)

[muraliD]

Describe the bug

1. page.js:10897 Unexpected token '<', "<!DOCTYPE "... is not valid JSON

2)Uncaught (in promise) Error: CLDR data for locale en is not loaded!

Isolated Example

No response

Reproduction steps

1take next js app router template from below project templates and examples
2.https://github.com/UI5/webcomponents-react/tree/main/examples/nextjs-app
3.add date range picker in any page . I have placed in todo list
return (
<DateRangePicker
onChange={function tie(){}}
onClose={function tie(){}}
onInput={function tie(){}}
onOpen={function tie(){}}
onValueStateChange={function tie(){}}
primaryCalendarType="Gregorian"
valueState="None"
/>
Initially displayed but after hard reload browser . date picker not displayed in browser.

Expected Behaviour

No response

Screenshots or Videos

No response

UI5 Web Components for React Version

"@ui5/webcomponents-react": "2.15.0",

UI5 Web Components Version

"@ui5/webcomponents": "2.15.0",

Browser

Chrome

Operating System

windows

Additional Context

No response

Relevant log output

Organization

No response

Declaration

• I’m not disclosing any internal or sensitive information.

[muraliD]

https://github.com/user-attachments/assets/38b14ad1-031f-44c8-b8cb-2b3d3afba050
https://github.com/user-attachments/assets/d7a368e6-40d0-48f9-b3e9-aff5553a9d9c

[muraliD]

https://sdk.openui5.org/1.120.17/resources/sap/ui/core/cldr/en.json ---- this resource file not loaded. this is main cause of this issue

[Lukas742]

Hi @muraliD

Thanks for reporting! I'll forward this issue to our UI5 Web Components Colleagues as the affected component is developed in their repository.

---

Hi Colleagues,
the issue is reproducible without our wrapper. You can find an isolated example here: https://github.com/Lukas742/ui5wc-next-approuter-cldr-issue/tree/main

[duygu-rmdn]

Hi @UI5/ui5-team-ctr-bal, I managed to reproduce the issue only once, but to be sure, could you please take a look?

[nnaydenow]

Hi @muraliD,

Please refer following duplicate incident: #12445

Regarding the original issue — the fix is to import the Assets files for the packages you’re actually using.
The error occurs only in development scenarios where the asset files are not automatically loaded.

For example, if your project uses @ui5/webcomponents and @ui5/webcomponents-fiori, import their assets directly.
You don’t need to import assets from @ui5/webcomponents-localization, as those are included automatically.