# Using Tailwind with local **URL:** \ **Category:** Support\ **Created:** [November 8, 2025, 2:25pm UTC](https://community.localwp.com/t/using-tailwind-with-local/51611 "2025-11-08T14:25:30Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![nickc](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nickc/32/21209_2.png) [@nickc](https://community.localwp.com/u/nickc)\ **Post date:** [November 10, 2025, 9:04am UTC](https://community.localwp.com/t/using-tailwind-with-local/51611/2 "2025-11-10T09:04:00Z")
Please can you check you are running Local 9.2.6 or higher and upgrade if not? We released a fix in that version to make sure that `NODE_ENV` is set to `development` instead of `production` (so that dev deps like `tailwindcss` are installed correctly during `npm install`). > [@Npm install Creates Empty node\_modules in LocalWP on Mac (Apple Silicon)](https://community.localwp.com/t/npm-install-creates-empty-node-modules-in-localwp-on-mac-apple-silicon/51133/2): > > @mst We just released Local 9.2.6 yesterday with a change that may fix this for you if you’re using npm in Local’s site shell with mostly dev dependencies: Site shells no longer inherit NODE\_ENV=production from Local. npm commands you run in site shells now use the default NODE\_ENV value (development). You can still override this in your shell config if needed. Please could you try upgrading to Local 9.2.6 if you haven’t yet to see if that solves your issue? You can find the latest version… If that doesn’t help, you might try `npm install --loglevel verbose` to see if there’s any explanation for the missing folders. --- _[View the full topic](https://community.localwp.com/t/using-tailwind-with-local/51611)._