That is correct. They ask you to republish the assets everything you do an update. This way they force you to rerun your own assets as well.
php artisan telescope:publish
Documentation: https://laravel.com/docs/7.x/telescope#installation
I'm building a simple spa with vue and laravel, developed as a laravel package, similar to horizon or telescope. I'm following the same folder structure as horizon and telescope, copying the compiled assets with laravel-mix after run "npm run dev" or "npm run prod", from mypackage/public to mypackage-test/public/vendor/mypackage.
The problem is the same here in this issue https://github.com/JeffreyWay/laravel-mix/issues/1762
I'm using:
My mix file:
mix.options({
terser: {
extractComments: false,
terserOptions: {
compress: {
drop_console: true,
},
},
},
}).setPublicPath('public')
.js('resources/js/app.js', 'public')
.sass('resources/sass/app.scss', 'public')
.version([
'public/assets/datatables/datatables.min.js',
'public/assets/datatables/datatables.min.css',
])
.copy('public', '../laravel-dash-test/public/vendor/dash');
The generated manifest:

The copied manifest:

Edit:
just made a clone of laravel telescope, executed npm run dev and guess what happens? The copied manifest has no hash.
Please or to participate in this conversation.