In this video, I refactor a Laravel Blade component to get rid of duplicate CSS and script tags—because if you drop a component like a date-picker multiple times, you really don’t want the same CDN assets injected again and again. I start with the “bad” version: the component includes the Flatpickr <link> and <script> directly inside the component, so every time I render two date pickers (join date and birth date), the HTML ends up with duplicate assets. That’s messy, harder to read, and it’s not great for performance. Then I clean it up properly using Blade stacks and the once/pushOnce directives. First, I update my layout to render assets in the right place: @stack('styles') in the head and @stack('scripts') at the bottom of the body. After that, inside the component, I push the Flatpickr CSS and JS into those stacks—so the layout controls where assets land. Finally, I eliminate duplicates by wrapping pushes in @once … @endonce, and then I show the cleaner approach: just use @pushOnce for both styles and scripts. The result is simple: no matter how many times I use the component, Flatpickr is included only once, while I can still customize initialization per input (class or ID) depending on what my app needs.