Download the PHP package edalzell/statamic-features without Composer

On this page you can find all versions of the php package edalzell/statamic-features. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of edalzell/statamic-features

Informations about the package statamic-features

Statamic Features

Self-contained features for Statamic, in an addon or in a site's own features/ directory. Built on edalzell/laravel-features: everything that package wires up for a feature still applies, and this one adds what a Statamic addon would register for itself.

Usage

This package is a laravel-features extension: its provider tags Extensions, and laravel-features hands every feature to it once the feature's Laravel pieces have booted. A feature keeps extending laravel-features' FeatureServiceProvider and just gains the folders below.

What's registered

Feature path What happens
src/Actions, src/Dictionaries, src/Fieldtypes, src/Modifiers, src/Scopes, src/Query/Scopes, src/Query/Scopes/Filters, src/Tags, src/Widgets Every concrete class of the matching type is registered. One level deep, as Statamic scans an addon
src/Subscribers Every class is passed to Event::subscribe()
src/UpdateScripts Registered against the addon the feature lives in. Skipped for a feature in a site, which has no package version to update from
resources/blueprints Blueprint namespace, named after the feature's slug: my-feature::thing
resources/fieldsets Fieldset namespace, named after the feature's slug: my-feature::common
routes/web.php Statamic web routes
routes/cp.php Control panel routes
routes/actions.php Action routes, prefixed with the feature's slug: /!/my-feature/...

Routes go through Statamic because Route::statamic() only exists once it has booted, after a feature's route files load. The provider sets these three as features.route_groups entries for every feature; override routeGroups() on one feature's provider to change them for that feature. Other route files keep the groups laravel-features gives them.

Control panel assets

Put them under resources/cp: every js/*.js is registered as a control panel script and every css/*.css as a stylesheet, and any other directory is published as-is:

They land in public/vendor/my-feature/, are tagged my-feature for vendor:publish, and are published automatically by statamic:install. To name them yourself instead, return statamic.scripts, statamic.stylesheets (lists of paths) and statamic.publishables ([from => to]) from the feature's options().

A Vite build is registered the way an addon's is, from a statamic.vite option — the entry point, or the same array an addon's $vite property takes:

Everything above is keyed by the feature's slug, so two features with the same name can't both be loaded; the second throws.

Vite builds and settings blueprints aren't handled per feature — those stay with the addon or site that hosts it.

Testing

All versions of statamic-features with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
edalzell/laravel-features Version ^2.0
statamic/cms Version ^6.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package edalzell/statamic-features contains the following files

Loading the files please wait ...