Download the PHP package geekwright/assetic-fork without Composer

On this page you can find all versions of the php package geekwright/assetic-fork. 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 geekwright/assetic-fork

Informations about the package assetic-fork

Assetic Build Status

This is a fork of Assetic

Assetic is a wonderful product, but sadly, it is lagging behind the PHP ecosystem. This fork is intended for use in PHP >7.1, depends on symfony/process 4, and passes tests in travis-ci.org

My sincere hope is that Assetic will be reborn and make this fork unnecessary. Until then I use:

composer require "geekwright/assetic-fork:2.*"

Assetic (original README)

Assetic is an asset management framework for PHP.

Assets

An Assetic asset is something with filterable content that can be loaded and dumped. An asset also includes metadata, some of which can be manipulated and some of which is immutable.

Property Accessor Mutator
content getContent setContent
mtime getLastModified n/a
source root getSourceRoot n/a
source path getSourcePath n/a
target path getTargetPath setTargetPath

The "target path" property denotes where an asset (or an collection of assets) should be dumped.

Filters

Filters can be applied to manipulate assets.

The filters applied to the collection will cascade to each asset leaf if you iterate over it.

The core provides the following filters in the Assetic\Filter namespace:

Asset Manager

An asset manager is provided for organizing assets.

The asset manager can also be used to reference assets to avoid duplication.

Filter Manager

A filter manager is also provided for organizing filters.

Asset Factory

If you'd rather not create all these objects by hand, you can use the asset factory, which will do most of the work for you.

The AssetFactory is constructed with a root directory which is used as the base directory for relative asset paths.

Prefixing a filter name with a question mark, as yui_css is here, will cause that filter to be omitted when the factory is in debug mode.

You can also register Workers on the factory and all assets created by it will be passed to the worker's process() method before being returned. See Cache Busting below for an example.

Dumping Assets to static files

You can dump all the assets an AssetManager holds to files in a directory. This will probably be below your webserver's document root so the files can be served statically.

This will make use of the assets' target path.

Cache Busting

If you serve your assets from static files as just described, you can use the CacheBustingWorker to rewrite the target paths for assets. It will insert an identifier before the filename extension that is unique for a particular version of the asset.

This identifier is based on the modification time of the asset and will also take depended-on assets into consideration if the applied filters support it.

Internal caching

A simple caching mechanism is provided to avoid unnecessary work.

Twig

To use the Assetic Twig extension you must register it to your Twig environment:

Once in place, the extension exposes a stylesheets and a javascripts tag with a syntax similar to what the asset factory uses:

This example will render one link element on the page that includes a URL where the filtered asset can be found.

When the extension is in debug mode, this same tag will render multiple link elements, one for each asset referenced by the css/src/*.sass glob. The specified filters will still be applied, unless they are marked as optional using the ? prefix.

This behavior can also be triggered by setting a debug attribute on the tag:

These assets need to be written to the web directory so these URLs don't return 404 errors.

Assetic is based on the Python webassets library (available on GitHub).

All versions of assetic-fork with dependencies

PHP Build Version
Package Version
Requires php Version >=7.1.0
symfony/process Version ~4.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 geekwright/assetic-fork contains the following files

Loading the files please wait ....