Weave Code
Laravel Svelte Preset Laravel Package
wewowweb/laravel-svelte-preset
A Laravel preset that scaffolds a Svelte frontend for new Laravel apps. It wires up the required build tooling and starter files, so you can skip manual Svelte setup and start building component-driven Laravel interfaces faster with sensible defaults.
Svelte frontend preset for Laravel.
Frequently asked questions about Laravel Svelte Preset
- What is wewowweb/laravel-svelte-preset and what does it do?
- It is a Laravel frontend preset that scaffolds a Svelte frontend for new Laravel applications, wiring up the required build tooling and starter files so you do not have to configure Svelte by hand. The stated goal is component-driven Laravel interfaces with sensible defaults. Because no composer.json or repository data was available at review time, treat claims about exactly which files and build steps it touches as unverified until you read the source.
- How do I install the Svelte preset in a Laravel app?
- Install it with Composer, most likely as a development dependency in a fresh Laravel application, then follow the preset command or post-install steps documented in the repository README. The exact artisan command and install flags are not confirmed in the release notes, so check the README and composer.json before running anything. Install into a throwaway branch or scratch app first rather than an existing project.
- Which Laravel versions does this package support?
- The v0.2.1 release notes state Laravel 9 support, with no published signal for Laravel 10, 11, or 12. Treat Laravel 9 as the only confirmed target and verify the illuminate/support constraint in composer.json yourself. Laravel 9 is past end-of-life, so a preset pinned to it can hold your application back.
- Which PHP versions does it require?
- The release notes say PHP 8 without naming a minor version, which is not a testable claim on its own. PHP 8.0 through 8.3 differ materially in deprecations and typing behavior, so confirm the exact php constraint and the CI test matrix. If it was only validated on 8.0, expect deprecation noise or failures on 8.2 and later.
- Is it safe to depend on a 0.x package like this in production?
- At 0.2.x, Semantic Versioning permits breaking changes in any minor bump, so a caret constraint such as ^0.2 can silently pull in a forced refactor. Pin the exact patch version, 0.2.1, and treat upgrades as deliberate, testable events. Wrap call sites behind a thin internal adapter so the preset can be swapped or forked without touching domain code.
- What files does the preset publish, and can I undo the install?
- The overview says it wires up build tooling and starter files, but the exact assets (config, migrations, routes, JavaScript scaffolding) are not documented in the material reviewed. After installing in a scratch app, enumerate everything it writes and confirm each item is removable. Keep the install in a single commit so you can revert cleanly.
- How is this different from Laravel Breeze, Jetstream, or wiring Vite with Svelte manually?
- Breeze and Jetstream are official Laravel starter kits that cover authentication and common UI stacks, while this package is a narrower preset focused on the Svelte frontend setup. A manual Vite plus Svelte configuration gives you the same outcome with documentation you control, and the official starter kits give you a maintained path. This preset mainly saves you the boilerplate of connecting Svelte to the Laravel build pipeline.
- Does it work with Laravel 10, 11, or 12?
- There is no stated support for Laravel 10, 11, or 12 as of v0.2.1, so do not assume forward compatibility. Installing it on a newer Laravel app may also force transitive upgrades or downgrades of framework and Symfony components. Check the composer.json constraints and run composer why-not before adopting it anywhere important.
- How should I evaluate or test this preset before adopting it?
- Read composer.json and the CI test matrix first, then install into a throwaway branch of a low-traffic Laravel 9 application. Confirm that nothing forces a framework downgrade and that any published config or migrations are reversible. Classify it as opportunistic rather than foundational until its public API surface and actual scope are understood.
- Who maintains this package and how actively is it updated?
- Ownership, release cadence, and any security disclosure process are not documented in the release notes reviewed. The v0.2.1 release bundled a GitHub Actions refresh alongside Laravel 9 and PHP 8 support, which suggests the pipeline had gone stale before that. Ask the maintainer directly about a 1.0 timeline, forward framework support, and a deprecation policy before depending on it long term.
Weaver
How can I help you explore Laravel packages today?