From f4adf01de26e14b1d3d68f4f94cb21e2d33e1c39 Mon Sep 17 00:00:00 2001 From: Willem Leuverink Date: Thu, 18 Jan 2024 10:28:50 +0100 Subject: [PATCH] wip --- docs/advanced-usage.md | 8 +++----- docs/local-modules.md | 1 - 2 files changed, 3 insertions(+), 6 deletions(-) diff --git a/docs/advanced-usage.md b/docs/advanced-usage.md index 1d29212..e9d15e5 100644 --- a/docs/advanced-usage.md +++ b/docs/advanced-usage.md @@ -25,11 +25,9 @@ You should apply this with consideration. You will save up on requests, but doin If a module supports per method exports, like `lodash` does, it is recomended to import the single method instead of the whole module & only retrieving the desired export later. ```html - - + - - + ``` ## Sourcemaps @@ -68,7 +66,7 @@ You may configure what paths are scanned by publishing the Bundle config file an ```php 'build_paths' => [ - resource_path('views/**/*.blade.php') + resource_path('views') ] ``` diff --git a/docs/local-modules.md b/docs/local-modules.md index 12b7b9e..2ce4cc0 100644 --- a/docs/local-modules.md +++ b/docs/local-modules.md @@ -5,7 +5,6 @@ image: "/assets/social-square.png" --- {: .note } - > Bundle is meant as a tool for Blade centric apps, like [Livewire](https://livewire.laravel.com), to enable code colocation with page specific JavaScript. Preferably the bulk your code should live inline in a script tag or in a [Alpine](https://alpinejs.dev) component. > > Local modules are a place to put boilerplate code. Like importing a single module & doing some setup, loading plugins etc. Writing complex code in here is discouraged. Abtract this away inside a blade component instead.