Pre-release documentation for v2. If you are looking for the v1 documentation.

Click here

This page addresses common issues that developers may encounter with WireUI and provides solutions. If you don't find a resolution for the specific problem you're facing, please consider checking the Issues page on the WireUI GitHub repository. If your issue hasn't been addressed there, don't hesitate to create a new Issue, and be sure to include as many details as possible.

If you've recently updated WireUI and are encountering issues, please ensure you consult the version-specific documentation before proceeding with this section.

Stay up to date with the latest developments in WireUI by following the author, @ph7jack , on Twitter.

If your assets (scripts and CSS files) are loaded via http:// instead of https:// , you can consider the following steps

1. Ensure that the `APP_URL` in your .env file is configured with an HTTPS prefix.


2. To clear Laravel's cache, execute the following command:

1php artisan optimize:clear

If you've come across the TypeError: require(...) is not a function error, it's essential to update your Tailwind-Forms to version "^0.3.0" . This issue commonly arises during Laravel Breeze installation.


ERROR in ./resources/css/app.css
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleBuildError: Module build failed (from ./node_modules/postcss-loader/dist/cjs.js):
TypeError: require(...) is not a function
1 ERROR in child compilations (Use 'stats.children: true' resp. '--stats-children' for more details)
webpack compiled with 2 errors


Adjust your Tailwind-Forms version, and then execute the npm update command.

1"devDependencies": {
2 "@tailwindcss/forms": "^0.3.0",
3 //..