Interestingly when I run the npm run ui:dev command I get tailwindcss v3.3.6 which is broken, but when I grab your css from the live template, it’s tailwindcss v3.3.5 which does work.
Pretty sure tailwindcss v3.3.6 doesn’t have anything to do with it as this is the diff between the 2 versions.
The older version didn’t have an updated app.css which was missing the styles, running any of the tailwind ui:dev or ui:build npm scripts would’ve re-synced app.css and included the missing styles.
Replacing the older CSS is what fixed it. I confirmed this by re-running the npm run ui:dev command, and it changed it back to 3.3.6, which then broke the functionality for me.
Here’s what I get when I do a manual DIFF between the two versions, and it’s a lot more than git hub is reporting, as my text compare is counting 10 difference changes:
The [data-collapse*] styles is what toggles sidebar visibility which are defined in tailwind.input.css. Running tailwind build should be including these styles in the generated app.css.
ui:dev produces an unminified build for development, ui:build produces an optimized build for production, both should include the same styles as per its tailwind configuration.
The next issue I am having is a strange one. Same template, deployed following the guidelines however I cannot seem to duplicate this issue with the live template (nor locally).
I am getting a 403 Forbidden when trying to fetch the /_framework/blazor.boot.json file.
I have traced it back to service stack showing it as forbidden by curling it from within the docker host vm: