# CSS files for composer theme are not loaded by DevKinsta **URL:** \ **Category:** Application Support\ **Created:** [September 9, 2026, 5:21am UTC](https://community.kinsta.com/t/css-files-for-composer-theme-are-not-loaded-by-devkinsta/7606 "2026-09-09T05:21:06Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![nicolepaton](https://avatars.discourse-cdn.com/v4/letter/n/7feea3/32.png) [@nicolepaton](https://community.kinsta.com/u/nicolepaton)\ **Post date:** [September 10, 2026, 7:37am UTC](https://community.kinsta.com/t/css-files-for-composer-theme-are-not-loaded-by-devkinsta/7606/6 "2026-09-10T07:37:14Z")
Hi Vladimir, Thanks very much for your detailed assistance. I have done step 1 and that did not work to fix the theme. It still looks the same. I have tried to do step 2, however I’m getting stuck at the composer install step. It does not appear to be available to install despite the fact that I did follow the steps outlined in the other thread: [Support for Composer - #10 by DavidME](https://community.kinsta.com/t/support-for-composer/175/10) . In that case I had installed in the tmp folder as per that thread. So this time when your steps above did not work I tried to follow the same steps again in the theme folder. Got through the install but the theme doesn’t have a package.json file and I’m not the original developer so I’m a bit unsure where to go from here. It still isn’t running in the browser in the same way as it does live on Kinsta where it also doesn’t have the package.json file. Here is my terminal log: root@bffba833335a:/tmp# composer install bash: composer: command not found root@bffba833335a:/tmp# cd /www/kinsta/public/outcomes/wp-content/themes/open-theme root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme# composer install bash: composer: command not found root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme# php -r “copy(‘[https://getcomposer.org/installer](https://getcomposer.org/installer)’, ‘composer-setup.php’);” root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme# php -r “if (hash\_file(‘sha384’, ‘composer-setup.php’) === ‘c8b085408188070d5f52bcfe4ecfbee5f727afa458b2573b8eaaf77b3419b0bf2768dc67c86944da1544f06fa544fd47’) { echo ‘Installer verified’; } else { echo ‘Installer corrupt’; unlink(‘composer-setup.php’); } echo PHP\_EOL;” Installer verified root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme# php composer-setup.php All settings correct for using Composer Downloading… Composer (version 2.10.3) successfully installed to: /www/kinsta/public/outcomes/wp-content/themes/open-theme/composer.phar Use it: php composer.phar root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme# composer install bash: composer: command not found root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme# php composer.phar install Composer could not detect the root package (\*ogdev/open-theme) version, defaulting to ‘1.0.0’. See [Troubleshooting - Composer](https://getcomposer.org/root-version) Installing dependencies from lock file (including require-dev) Verifying lock file contents can be installed on current platform. Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you run `composer update` or `composer update `. Nothing to install, update or remove Generating autoload files root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme# npm install npm WARN saveError ENOENT: no such file or directory, open ‘/www/kinsta/public/outcomes/wp-content/themes/open-theme/package.json’ npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN enoent ENOENT: no such file or directory, open ‘/www/kinsta/public/outcomes/wp-content/themes/open-theme/package.json’ npm WARN open-theme No description npm WARN open-theme No repository field. npm WARN open-theme No README data npm WARN open-theme No license field. npm notice This endpoint is being retired. Use the bulk advisory endpoint instead. See the following docs for more info: [npm Registry API](https://api-docs.npmjs.com/#tag/Audit) up to date in 0.362s found 0 vulnerabilities root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme# npm run build npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /www/kinsta/public/outcomes/wp-content/themes/open-theme/package.json npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, open ‘/www/kinsta/public/outcomes/wp-content/themes/open-theme/package.json’ npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/\_logs/2026-09-10T07\_27\_27\_548Z-debug.log root@bffba833335a:/www/kinsta/public/outcomes/wp-content/themes/open-theme# Thanks again for trying to help. --- _[View the full topic](https://community.kinsta.com/t/css-files-for-composer-theme-are-not-loaded-by-devkinsta/7606)._