Download the PHP package nickdekruijk/leap-template without Composer
On this page you can find all versions of the php package nickdekruijk/leap-template. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download nickdekruijk/leap-template
More information about nickdekruijk/leap-template
Files in nickdekruijk/leap-template
Package leap-template
Short Description Frontend website template scaffolding for nickdekruijk/leap: the leap:template and leap:content commands. Install with composer require --dev.
License MIT
Informations about the package leap-template
Leap Template
Frontend website template scaffolding for nickdekruijk/leap:
the leap:template and leap:content commands, plus the stubs they copy into your
project. It is dev-only tooling — install it with --dev so it (and its commands)
are absent from production entirely.
Installation
Leap itself is a runtime dependency (the admin panel runs in production); only the scaffolding is dev-only. So install two packages, like Laravel's own framework + Pint:
Why
nickdekruijk/leapmust be a normal (non-dev) require: this package depends on leap, but if you onlyrequire --dev leap-template, leap comes in as a dev-transitive dependency andcomposer install --no-devon production removes it — taking the admin panel with it. leap has to be a direct non-dev requirement of your app.
On production (composer install --no-dev) leap-template is not installed, so
leap:template/leap:content don't exist there — zero footprint.
Live demo
leap.nickdekruijk.nl is a stock leap:template install —
that site is what these stubs produce. Log in on
/admin with [email protected] / leapdemo and
change anything; the site resets to its seeded state 15 minutes after the last change.
Commands
Both refuse to run on APP_ENV=production without --force (like Laravel's migrate).
Documentation
The template and content types are documented in the leap repo:
Versioning
Tracks leap's major line — this package requires nickdekruijk/leap: ^1.0, so only a
breaking leap release (2.0) is paired with a new leap-template major. The two packages
are released in lockstep at the same version number, but within the major you can update
either on its own.
Pushing a tag publishes a GitHub release automatically, with that version's CHANGELOG.md section as its notes — so the changelog stays the only place a release is written. A tag whose version has no changelog section fails the workflow rather than publishing an empty release.
License
MIT.