WireKit v2.18.2
Patch release — setup-documentation corrections. No code changes: the package renders exactly as it did in 2.18.1. What changed is the getting-started walkthrough, which in two places described a setup step inaccurately enough to leave a first-time reader with a failing build.
Documentation
- Getting started told readers to create a
resources/js/bootstrap.jsthat their build cannot resolve. The page treated a missingbootstrap.jsas a file to be recreated from the block shown. That holds forlaravel/laravel, which ships the file and listsaxiosinpackage.json— but the Livewire Starter Kit ships neither, so following the instruction there ended infailed to resolve import "axios"on the nextnpm run build. The section now distinguishes the two scaffolds, states plainly that creating nothing is the correct action when axios is absent (WireKit never uses it), and gives the install command for readers who want Laravel's baseline regardless. - The same block described the axios global as a Livewire requirement. It is not: Livewire issues its own
fetch()calls and never readswindow.axios. The comments said otherwise, which made an explicitly optional step read as mandatory. - The first-Livewire-page walkthrough named a command without the flag that produces its files. The paragraph promised
app/Livewire/Showcase.phpandresources/views/livewire/showcase.blade.phpwhile namingmake:livewirealone. Livewire 4 defaults to a single-file component, so readers who ran it as written gotresources/views/components/⚡showcase.blade.phpand could not find any file the walkthrough went on to edit. The flag is now stated before the claim, together with what happens without it. - Code block and the Chart.js advanced guide now install what their examples import. Both showed an import for a package (
highlight.jsandchart.jsrespectively) whose install step lived on another page.