Laravel Backpack Vapor Guide

vapor.yml

    build:
      - 'composer install --no-dev --classmap-authoritative'
      - 'php artisan event:cache'
      - 'sh ../../../utils/vapor_build_purge.sh'

vapor_build_purge.sh

#!/usr/bin/env bash

rm -rf public/packages || true
cp -r  vendor/backpack/crud/src/public/packages public/packages
find public/packages -print | wc -l
rm -rf public/packages/tinymce
rm -rf public/packages/summernote
rm -rf public/packages/simplemde
rm -rf public/packages/ckeditor
rm -rf public/packages/jquery-colorbox
rm -rf public/packages/jquery-cropper
rm -rf public/packages/cropperjs
rm -rf public/packages/bootstrap-iconpicker
rm -rf public/packages/bootstrap-colorpicker
rm -rf public/packages/bootstrap-datepicker
rm -rf public/packages/bootstrap-daterangepicker
rm -rf public/packages/nestedSortable
rm -rf public/packages/places.js
rm -rf public/packages/pc-bootstrap4-datetimepicker
rm -rf public/packages/select2/dist/js/i18n
rm -rf public/packages/select2/dist/js/i18n
rm -rf public/packages/source-sans-pro
rm -rf vendor/backpack/crud/src/public/packages
rm -rf compose
find public/packages -name '*.md' -delete
find public/packages -name '*.html' -delete
find public/packages -name '*.txt' -delete
find public/packages -name '*.json' -delete
find public/packages -name '*.gzip' -delete
find public/packages -name '*.map' -delete

find public/packages -print | wc -l

It turns out the vapor manifest (vapor.yml) does have support for an ignore section (at the root, not per environment), in which user-defined file and directory ignores may be declared.

• See BuildProcess/RemoveIgnoredFiles.php

Although, when the list is this long, I think I'd prefer this approach. Or, maybe a feature request to just put these into a .vaporignore file instead.