Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

Jijiri89's avatar

My tailwindcss is not applied on the production

Jijiri89 Jijiri89 Posted 15 hours ago Hello everyone. Kindly help I have developed laravel and livewire using breeze and tailwindcss. In my my local machine, my project works perfectly if I run npm run dev and php artisan serve command. Before I uploaded it to cpanel, I ran npm run build. When I uploaded it to the cpanel, the tailwindcss is not loaded. The welcome page works fine. In cpanel, what I did is

I created a new folder, named myapp in the root of the fife manager, I have uploaded the zipped folder of my entire project into the folder I have just created. I extracted it and moved all files into the newly created folder by name, myapp. I created mysql database and edited env file with the database credentials. I edited the index.php file to include the folder that has my project. I then moved all the public folder contents into the public to public_html folder. When I visited my website url, I got error that vite manifest not found at public /build. I then moved the build file back to the public folder and this time the project run but the tailwind css is not applied. Kindly help me have to set my tailwindcss to work in cpanel

0 likes
7 replies
hupp's avatar

@jijiri89 run the

npm install
npm run production

on production server.

hupp's avatar

@jijiri89

<link rel="stylesheet" href="{{ asset('css/app.css') }}">

Check your style loads using like this.

TerrePorter's avatar

run the npm command on your dev server, then copy the files in the public/build to your server. if your asset links are good then it should work

Snapey's avatar

research better ways of deploying your app. You cant run all those steps everytime you want to update the site!

thinkverse's avatar

Sounds like you never built the production build with npm run build before you zip:d up your site.

Running npm run dev starts a temporary server that serves your assets on that machine for the duration that the command is running.

To build permanent production builds use the npm run build command, and include everything generated in the /public/build folder in your .zip file. That should be the manifest.json and everything in the assets folder.

If you're storing your site in a git repo and use that to pull your site to your server and cannot run npm commands on the server to build your production assets there. Then you need to edit your .gitignore and remove the /public/build line to start tracking the production builds and commit them each time you update your CSS or JavaScript.

Please or to participate in this conversation.