From f8fd83f60978ca2fd55b73585714c663d54fc476 Mon Sep 17 00:00:00 2001 From: Willem Leuverink Date: Thu, 20 Jun 2024 21:36:31 +0200 Subject: [PATCH] update docs --- docs/local-modules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/local-modules.md b/docs/local-modules.md index 3a40cc1..4b2115f 100644 --- a/docs/local-modules.md +++ b/docs/local-modules.md @@ -91,7 +91,7 @@ When importing this module you can omit the `as` prop. Axios will be available o Note that your consuming script still needs to be of `type="module"` otherwise `window.axios` will be undefined. -It is also good to note that Bundle's primary goal is to get imports inside your Blade template. While the init strategy can be very powerful, it is not the place to put a lot of business code since can be a lot harder to debug. +It is also good to point out (again) that Bundle's primary goal is to get imports inside your Blade template. While the init strategy can be very powerful, it is not the place to put a lot of business code since can be a lot harder to debug. {: .warning } > Code splitting is [not supported](https://laravel-bundle.dev/caveats.html#code-splitting). Be careful when importing modules in your local scripts like this. When two script rely on the same dependency, it will be included in both bundles. This approach is meant to allow setup of more complex libraries. It is recommended to add complex code inside your templates instead and only use Bundle for importing libraries.