orrison
orrison
PostsComments
FFilament
Created by orrison on 8/11/2023 in #❓┊help
Issue with deployments after adding viteTheme() to Panel
It is not. It is during a fresh deployment with a tool like Deployer or Laravel Envoyer. Or really during any fresh setup of the application. This is due to viteTheme() looking for the Vite manifest file. I have solved for this by changing my deployment process to work like this: 
composer install -q --no-ansi --no-interaction --no-scripts --no-progress --prefer-dist

npm ci
npm run build

composer after-autoload
composer install -q --no-ansi --no-interaction --no-scripts --no-progress --prefer-dist

npm ci
npm run build

composer after-autoload
With my composer.json scripts looking like: 
{
  "post-autoload-dump": [
      "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
      "@after-autoload"
  ],
  "after-autoload": [
      "@php artisan package:discover --ansi",
      "@php artisan filament:upgrade"
  ],
}
{
  "post-autoload-dump": [
      "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
      "@after-autoload"
  ],
  "after-autoload": [
      "@php artisan package:discover --ansi",
      "@php artisan filament:upgrade"
  ],
}
To keep local functionality the same, but avoid this issue during deployments
4 replies