Hey @Grldk , thanks a lot for the report!

I'll have a look at it this weekend and hopefully there's an easy and non-breaking solution to this :) After all, assets are already pre-built and come part of the package, so there should be no need for eval use.

Thanks for your quick reply!

It's an annoying consquence of using Vue.. And of using CSP in the first place, it's not widespread enough for people to take it into account unfortunately..

I've tried to fix it for Laravel Horizon, but failed (PR got reverted), and I'm not sure why. I don't really have any Vue experience, and not enough time or a use case to dive into it to see what the issue is.. Hope you can fix it for this package.. Thanks for your time!

Hey @arukompas, had any luck with this?

Hey @Grldk , I tried it for a while but I couldn't figure out how to make it CSP-friendly.

I have another idea, though, just not sure if it would work for your setup.

Would it be possible to override the CSP policy just for Log Viewer? Here's an example:

1. Publish the Log Viewer's layout - php artisan vendor:publish --tag=log-viewer-views
2. Open resources/views/vendor/log-viewer/index.blade.php
3. Add a meta tag to set a different CSP policy for this page

    <!-- ... -->
    <link rel="shortcut icon" href="{{ asset(mix('img/log-viewer-32.png', 'vendor/log-viewer')) }}">
+   <meta http-equiv="Content-Security-Policy" content="default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self';">

    <title>Log Viewer{{ config('app.name') ? ' - ' . config('app.name') : '' }}</title>
    <!-- ... -->

This will allow unsafe-evals and, based on my testing, allows Log Viewer to work.

Let me know how it goes!