Weave Code
Scratch Laravel Package
laravel-bridge/scratch
A lightweight Laravel bridge for scratch work: temporary storage, throwaway records and sandboxed experiments kept out of your main tables. Simple setup, sensible defaults and a clean API make it handy for prototyping, testing and quick one-off tasks.
For project from scratch
Frequently asked questions about Scratch
- What is laravel-bridge/scratch used for?
- It's a lightweight Laravel bridge for scratch work: temporary storage, throwaway records and sandboxed experiments kept out of your main tables. It's aimed at prototyping, testing and quick one-off tasks rather than durable application data. Simple setup, sensible defaults and a clean API are the advertised selling points.
- How do I install laravel-bridge/scratch?
- Install it with composer require laravel-bridge/scratch and pin to ^1.7, the release that added PHP 8.0 support. Run composer update laravel-bridge/scratch in isolation rather than a blanket update, then review the lockfile diff for transitive churn. Most Laravel packages register a service provider through package discovery, but confirm that in the README.
- How do I configure laravel-bridge/scratch?
- The README excerpt available here is empty, so the exact config keys aren't documented in this record. Laravel packages commonly publish a config file via php artisan vendor:publish, so check the repository for the publish tag and default values. Until you confirm them, keep the package's settings explicit in your own config rather than relying on defaults.
- Which PHP and Laravel versions does laravel-bridge/scratch support?
- The only documented signal is v1.7.0 adding PHP 8.0 support; the composer.json Laravel constraint isn't in the record. Check with composer why-not php 8.2 and composer why-not laravel/framework ^11.0 after requiring the package. Also ask whether 8.0 was added alongside an existing floor or lowered the minimum.
- Does laravel-bridge/scratch work with Laravel 11 and Laravel 12?
- That can't be confirmed from the available evidence, and it matters: Laravel 11 and 12 require PHP 8.2 or newer, while the only changelog entry mentions PHP 8.0. Inspect the package's composer.json for the illuminate/support or laravel/framework constraint. If it caps below the majors you run, the package is not suitable for new work.
- Is laravel-bridge/scratch safe to use in production?
- Treat it as a prototyping and testing aid, not a system of record, since its purpose is throwaway records and sandboxed experiments. Confirm whether it's a leaf dependency or sits on a hot path such as persistence, auth or queue before adopting. Also verify PHP 8.0 support is actually covered in CI so failures surface in tests rather than production.
- How do I test code that uses laravel-bridge/scratch?
- Point the package at a test database or in-memory connection and reset state between tests so scratch data doesn't leak. Because the README excerpt isn't available in this record, check the docs for any test helpers or fakes the package ships. Isolating scratch storage per test is the safest default.
- What are alternatives to laravel-bridge/scratch?
- You can get the same outcome with a dedicated database connection, in-memory SQLite for tests, or Laravel's RefreshDatabase trait and transaction wrapping. Separate scratch tables in your own migrations are another option with nothing extra to audit. Weigh whether a Composer dependency buys you enough over a few lines of configuration.
- How actively is laravel-bridge/scratch maintained?
- The visible signal is a 1.x line at v1.7.0 whose headline change is PHP 8.0 support, an end-of-life runtime since November 2023. There's no CI configuration or 2.0 roadmap in the record, so release cadence can't be verified. Ask the maintainer about release frequency and whether the 8.0 line is a maintenance branch.
- Does laravel-bridge/scratch support PHP 8.2 and 8.3?
- Not documented: the record only shows PHP 8.0 support added in v1.7.0. Run composer why-not php 8.3 to surface the effective ceiling, and check whether 8.2 and 8.3 are in the CI matrix. A claim of 8.0 support is often just a constraint change and may be untested.
Weaver
How can I help you explore Laravel packages today?