Weave Code
Definitely Not V3 Laravel Package
statamic/definitely-not-v3
A lightweight Statamic addon with a playful name, definitely-not-v3 is not an upgrade path to Statamic v3. It provides a small, self-contained utility for existing Statamic projects, aimed at developers who want a simple addon without changing their stack.
Really, this is not v3!
Frequently asked questions about Definitely Not V3
- What is statamic/definitely-not-v3 and is it actually a Statamic v3 upgrade path?
- It is a tongue-in-cheek Composer package whose name is the joke: it is definitely not Statamic v3 and is not an upgrade path. The description frames it as a lightweight addon, while prior engineering assessments read the repository as a bare addon skeleton with PSR-4 autoloading and an auto-discovered service provider. Either way, it provides no admin surface, auth, or domain logic. Treat it as a naming joke and a possible layout reference, not a migration tool.
- How do I install statamic/definitely-not-v3 in a Laravel project?
- Technically it installs like any other Composer package with composer require statamic/definitely-not-v3. There are no config files to publish and no service provider to wire up by hand because the skeleton uses auto-discovery. However, the package is archived and its constraints are unpublished, so do not add it to a live application. If you want to inspect it, install it in a disposable Laravel project instead.
- Does statamic/definitely-not-v3 actually implement the version guard its description advertises?
- That is the central discrepancy. The description claims a version guard that asserts your install is not v3 and fails loudly on version drift, but prior engineering assessments found only an empty addon skeleton. Metadata alone cannot settle it, and zero dependents provide no evidence either way. The only reliable answer is to read the repository source end-to-end rather than trusting the description or release notes.
- Which Laravel and Statamic versions does statamic/definitely-not-v3 support?
- The supported PHP, illuminate/*, and Statamic ranges are not documented. The 2018-11-07 release date and archived status mean it encodes Statamic v2 and Laravel 5.x-era addon conventions. Addon bootstrapping and service-provider registration have moved on since then, so expect to correct the manifest constraints rather than reuse them. Do not assume the implied modern compatibility from the description is verified.
- Is statamic/definitely-not-v3 safe to use in production?
- No. It is archived, so there are no security fixes, dependency bumps, or compatibility work, and zero dependents mean no ecosystem evidence that it boots against currently supported frameworks. A 3.0.2 release whose changelog reads only Stuff is a punchline, not a change record. Treat it as a one-off read or a pattern to vendor, not a runtime dependency.
- Does statamic/definitely-not-v3 require any configuration or service provider registration?
- The package advertises zero configuration, no publishable config files, and no manual service-provider wiring. That matches the skeleton reading, where an auto-discovered provider exists but there is nothing meaningful to configure. The tradeoff is that zero configuration also means zero capability you can rely on. Nothing should break, but nothing should be expected to happen either.
- How can I test statamic/definitely-not-v3 or verify it works with my app?
- There is no documented test suite to lean on. Review the source end-to-end, which is small enough to do in under an hour, and try composer require in a throwaway Laravel app pinned to your framework majors. Confirm that the autoloader resolves and the service provider boots without errors. Do not rely on the release history, since the changelog is intentionally uninformative.
- What are the alternatives to statamic/definitely-not-v3 for scaffolding a Statamic addon?
- Use Statamic's first-party addon scaffolding, such as make:addon or the official boilerplate, which covers the same ground with an active maintainer. If you only want the skeleton shape, copy the directory structure, service provider, and composer.json into an internal package under your own namespace. For the version-guard idea, a Composer constraint or a CI check expresses it without adding a dependency. All of these are safer than depending on an archived joke package.
- Why is statamic/definitely-not-v3 archived and what does that mean for maintenance?
- It is archived with its last release in 2018, which suggests the joke landed and the package was retired rather than actively maintained. Whether that was intentional or abandonment, the operational answer is the same: no security patches, no dependency bumps, and no compatibility work. An archived 2018 package in composer.json will also trip supply-chain scanners and complicate your next framework upgrade. If the skeleton is useful, vendor it internally instead of depending on it.
- Can I remove statamic/definitely-not-v3 easily if I change my mind?
- Yes, removal is trivial because it has no runtime data, no published config, and no opinionated defaults. A composer remove drops the package and its auto-discovered provider without leaving much behind. The cleaner path, though, is not to add it to a live app in the first place. If you already copied the skeleton into an internal package, simply inline the files and drop the external constraint.
Weaver
How can I help you explore Laravel packages today?