Style Migration Troubleshooting
When the local environment style is abnormal, follow this procedure to troubleshoot:
- CDN introduction check: Confirmation of the local HTML file's
headincludehttps://cdn.tailwindcss.comLayout.dev uses v3.3 by default, and it is recommended to use it locally via thescript src=https://cdn.tailwindcss.com/3.3.5Specify the same version - PurgeCSS Configuration: If using the build tool, check the
tailwind.config.jsDoes it containcontent: [.html, ./src/**/*.{js,ts,jsx,tsx}]Configuration to avoid production environment styles being purged - Font File Handling: Check the box when exporting a projectInclude Web Fontsoption, or locally via the
@import url(https://fonts.geekzu.org/css2?family=Inter)Manual introduction of Inter fonts
The ultimate solution: 1) By exporting the panel'sExport with BuildGenerate a version that includes the full Tailwind build; 2) or run it after installing Tailwind CSS locallynpx tailwindcss -i ./src/input.css -o ./dist/output.css --watchCompile styles in real time.
This answer comes from the articleLayout.dev: an AI development tool for rapid UI generationThe
May not be reproduced without permission:AI productivity tools " How to solve the problem of Tailwind style not working after exporting project to local environment?
English 
简体中文 
日本語 
Deutsch 
Português do Brasil