For the first edition of 2026 of the monthly meetup, we will discuss the latest updates from the App Platform for creating and building DHIS2 web applications. Some highlights include:
The new updated CLI for scaffolding new applications
Updates to the UI library (and some coming breaking changes )
New hook contributed to App Runtime by @Davis from HISP Tanzania
We also want to take the chance to hear your feedback and suggestions for improvements of the CLI and the DHIS2 web applications ecosystem. So come over prepared with your requests!
The meetup is on 2026-01-08T10:00:00Z. To register, please click this link. You will receive a DM on the CoP with the direct zoom link before the event! If you have registered before, you can use the same link.
Here is a teaser for the new CLI with updated templates and improved structure and functionality. I hope to see you all tomorrow for a first look and discuss all your ideas to improve it.
Give it a try already with pnpm create @dhis2/app (or npm instead of pnpm if you prefer)
So, using an external DHIS2 instance (like Login app | DHIS2) ends up in a warning message Chrome in the login response headers call. The message is “This set-cookie was blocked because it has the samesite=lax attribute but come from cross-site response witch was not the response to top-level navigation”.
Also, I tried the alternative parameter --proxy (as described in the doc). But the response to the call http://localhost:8080/api/loginConfig is (failed)net::ERR_CONNECTION_REFUSED.
Yes, you need to add --proxy for servers that have SameSite header (like DHIS2 play servers)
To use the proxy option with npm, you have to pass an extra --, i.e. npm start -- --proxy https://play.im.dhis2.org/stable-2-42-3-1 (notice the extra – described in npm docs)
)
