Download the PHP package kanopi/pack-asset-loader without Composer

On this page you can find all versions of the php package kanopi/pack-asset-loader. 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 kanopi/pack-asset-loader

Informations about the package pack-asset-loader

Kanopi Pack Asset Loader

PHP library for use in PHP and WordPress applications to facilitate development using Kanopi Pack (wrapper for Webpack) and deployment of its published assets. Loader provides a systematic method to enqueue scripts and styles produced from Webpack entry points.

Documentation Reference

Classes

Loader Configuration Class

All assets are registered with the following sets of configuration parameters:

Parameter Default
Asset Manifest Path None
Development Styles In Head False
Handle Prefixes kanopi-pack-
Production Domains None
Script Path /assets/dist/js/
Static Path /assets/dist/static/
Style Path /assets/dist/css/
Version None
Class Method Description
__construct( ?string $_version = null, ?array $_production_domains = null, ?string $_asset_manifest_path = null, ?string $_handle_prefix = null, ?string $_script_path = null, ?string $_style_path = null, ?string $_static_path = null ) Override any default values associated with the configuration

Asset Loader API Class

The underlying class, which coordinates the load of assets from a Kanopi Pack configuration, is located at Kanopi\Assets\AssetLoader.

Webpack generates two special script types which are loaded at specific times, though are optional based on other assets present in the app/site:

  1. Runtime - Present to coordinate modules shared between multiple packages. For instance, if app1.js and app2.js share Vue3, a runtime file (default handle of runtime) is generated and must be loaded before either.
  2. Vendor - Contains any third-party imported modules, either listed under the package.json key of require, or referenced in an entry point with @import <named_node_module>. For instance, if app1.js and app2.js share Vue3, a vendor file (default handle of vendor) is generated and must be loaded before any Runtime and App entry points. NOTE - Webpack may also generate another module coordinating file, default handle of central, which is always present on the Dev Server.
Class Method Description
__construct( string $_base_url, ?string $_development_url, Model\LoaderConfiguration $_configuration ) Coordinate the asset loader, based on a set of production and development URLs, and path configurations
enqueue_assets() Helper function generates a series of WordPress wp_enqueue_* calls
in_development_mode(): bool Flag to tell whether the assets are currently loaded in Production or Development mode
register_applications( string $_handle, array $_dependencies = [] ) Register an application (contains both script and styles), via entry point handle and any preceding script handles (not styles)
register_runtime_script( string $_handle, array $_dependencies = [] ) Register the Webpack runtime script, via entry point handle and any preceding scripts
register_script( string $_handle, array $_dependencies = [] ) Register a script, via entry point handle and any preceding scripts
register_style( string $_handle, array $_dependencies = [] ) Register a style, via entry point handle and any preceding styles; In development mode, these are ignored.
register_vendor_script( string $_handle, array $_dependencies = [] ) Register a Webpack generated vendor script, via entry point handle and any preceding scripts

WordPress Enqueue Registry

Coordinates enqueuing assets within WordPress with the Front-end and Block Editor for Kanopi Pack.

API

The main WordPress registration class is located at Kanopi\Assets\Registry\WordPress.

Class Method Description
__construct( LoaderConfiguration $_configuration ) Configures the asset manifest and versioning features
register_block_editor_scripts( callback $_closure ) Wrapper to enqueue scripts and styles for the Block Editor
register_frontend_scripts( callback $_closure ) Wrapper to enqueue scripts and styles on the site front-end
update_block_editor_priority Configure the WordPress action priority of the loaded scripts and styles in the Block Editor
update_frontend_priority Configure the WordPress action priority of the loaded scripts and styles on the front-end

WordPress Configuration Note

In default implementations, the package assumes the constant KANOPI_DEVELOPMENT_ASSET_URL is defined before calling the package, otherwise only Production mode is available

WordPress Examples

Single set of assets in the active WordPress theme

Consider this sample set of Kanopi Pack entry points:

An example loader sequence is as follows, though it's recommended this be placed in a module or some other structure.

Adding a New Script or Style

When a new script of style is added, add the handle to the appropriate registration function.

Consider adding a new script and style for a Song post type to the site in the previous example.

The new configuration becomes:

Adding Gutenberg Blocks to the Site

When a new script of style is added, add the handle to the appropriate registration function.

Consider adding new Song Listing and Testimonial blocks to the site in the previous example.

It is strongly recommended to add all of the blocks to the site through a common script with an auto-loader function for HMR. Also, styles written modularly for each block can be included in their front-end stylesheets and separately included in a Block Editor specific sheet, blocks-theme entry point.

Both blocks, in this example, are registered both in PHP and in the block-editor entry point. Both blocks contain front-end script functionality, the song listing is a widget on all pages so is included here. The testimonial block, however, is situational, so we will let the block.json on the PHP side register its scripts and styles.

The new configuration becomes:

All versions of pack-asset-loader with dependencies

PHP Build Version
Package Version
Requires php Version >=7.4
ext-json Version *
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 kanopi/pack-asset-loader contains the following files

Loading the files please wait ....