Use CSS Variables instead of the in-built :export that is in the built CSS #319
Description
This weekend when trying to resurrect the Dashku application, I encountered an issue trying to get Next.js 16 to load the application.
It was failing to build or run because of an issue of an unidentified instruction in the CSS called :export.
A conversation with ChatGPT 5.2 suggested replacing the use of that :export with CSS variables instead.
The workaround I was able to deploy in time was to use the --webpack flag on the next commands when running dev and build. That worked, but it is a temporary workaround and ideally we need the library to be able to work with Next.js apps that use Turbopack, and eventually with apps built using other frontend frameworks like Svelte.
To fix the issue with @anephenix/ui and make it work with Next.js 16 using Turbopack, you’ll need to switch to using CSS variables rather than the :export (which webpack supports).