To automate publishing of the BladewindUI files every time you run composer update, you can add the following lines to your composer.json file under the scripts key. If you access the Bladewind components using the dot syntax, you will need to also republish the components view files by running the command below. Php artisan vendor:publish -provider="Mkocansey\Bladewind\BladewindServiceProvider" -tag=bladewind-public -force Run the command below to publish the Bladewind assets. It is important to republish the assets after every update to pull in any new css and js changes. Running composer update at the root of your project will pull in the latest version of BladewindUI. If you intend to use bladewindUI in a Laravel 8.x project, please do well to read this. You can access any of the Bladewind components using the dot syntax The Bladewind components now exist in resources > views > components > bladewind. Php artisan vendor:publish -provider="Mkocansey\Bladewind\BladewindServiceProvider" -tag=bladewind-components -force To use the usual dot syntax when calling Laravel components, you will need to publish the BladewindUI views to your views directory using the command below. Try to set them to your needs and then use. This is because we are serving the views from the package's directory in vendor/mkocansey. In your settings, there is no specific option for setting a code style for 'blade' files, but phpStorm can recognize the language of each code line in your blade.php file, so it will apply either the HTML code style in HTML lines, or JS code style in JS lines and so on. You will notice from the example above we had to use two colons after x-bladewind. You are now ready to start using any of the BladewindUI components in your application you are already using AlpineJs in your project The Datepicker and Timepicker components require AlpineJs 3.x to work. Some devs are using VS Code, some are using PhpStorm. you can ignore this if you already have animate.css () in your project Our time is getting bigger and bigger, and we we need to have consistent code formatting in our repos. this is required for the animation of notifications and slide out panels ![]() From v2.0.0, the Bladewind assets were moved from public to public/vendor to enable Bladewind sit with any third party libraries you may already have in your project
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |