Continuing the discussion from React with tailwindcss for node-red?:
Thanks to @TotallyInformation for taking the time to explain his concerns about Tailwind. Based on his suggestions, I split package into a separate plugins instead of keeping it as part of the main package.
The first modules are now available on npm (better Tailwind class completion - soon).
- @aaqu/fromcubes-react – React portals for Node-RED, built at deploy time, with live WebSocket data binding.
- @aaqu/fromcubes-tailwind – Tailwind CSS 4 generation with editor class completion.
- @aaqu/fromcubes-assets – static files for portals, managed from a Node-RED sidebar.
- @aaqu/fromcubes-auth-headers – identity provider using
x-portal-user-*headers set by a reverse proxy.
The main goal is to make the project less dependent on specific technologies and easier to extend. React will remain the foundation, but other parts, such as styling and asset management, are now separated into independent packages. This should make it easier to change or replace individual components in the future and, in theory, allow others to develop their own plugins for fromcubes-react.
The old version will stay in the repository.
