Download the PHP package sitegeist/slipstream without Composer

On this page you can find all versions of the php package sitegeist/slipstream. 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?

Informations about the package slipstream

Sitegeist.Slipstream

Header requirements for presentational fusion

"Quantum slipstream transcends the normal warp barrier by penetrating the quantum barrier with a focused quantum field."

The slipstream package allows defining header requirements with presentational fusion by labeling the required tags with a unique attribute. They are later deduplicated and moved to the target position. This allows defining additional the JS and CSS requirements directly with the presentational fusion components.

Authors & Sponsors

The development and the public releases of this package is generously sponsored by our employer sitegeist.

Usage

You can mark any HTML fragment to be moved to the head of the document by adding a data-slipstream attribute.

The slipstream middleware will parse the entire page and detect all those tags. The tags are then removed from the original location and are appended to the header. Every tag is added only once, so if multiple components require the same JS, only one is added to the given location.

Alter target by tag name

By defining the data-slipstream attribute with an tag name, the target can be altered.

Using CSS selector (id or class name) as target

If you want to target a specific element with an id or class name you can also use a selector prefixed with an # (id) or an . (class name). The string itself musst start with a letter, underscore or hyphen. No spaces are allowed. Also multiple id and classes combinations won't work, only a single class name or id works.

Using XPATH selector as target

Location of the tag

To prepend the tag to the given target, you can add the data-slipstream-prepend attribute:

To place a tag before or after a specific tag, you can add the data-slipstream-before or data-slipstream-after attribute:

Debug mode

When the setting Sitegeist.Slipstream.debugMode is enabled, HTML comments are rendered to mark where tags were removed and inserted. This is enabled in Development Context by default.

Remove slipstream attributes

If the setting Sitegeist.Slipstream.removeSlipstreamAttributes is enabled, the attributes from slipstream get removed. This is disabled in Development Context by default.

Inner working and performance

The slipstream HTTP middleware will modify all responses with an active X-Slipstream: Enabled HTTP header. This header is added to Neos.Neos:Page and Sitegeist.Monocle:Preview.Page already, so this will work for Neos and Monocle right away. You will have to add the header X-Slipstream: Enabled for other controllers.

Since the response body is parsed and modified, this adds a minor performance penalty to every request. However the package is designed to work together with Flowpack.FullpageCache, which will in turn cache the whole result and mitigate the slight performance drawback.

Installation

Sitegeist.Slipstream is available via packagist run composer require sitegeist/slipstream.

We use semantic-versioning so that every breaking change will increase the major version number.

Contribution

We will gladly accept contributions. Please send us pull requests.

All versions of slipstream with dependencies

PHP Build Version
Package Version
Requires neos/flow Version ^8.0 || ^9.0 || dev-master
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 sitegeist/slipstream contains the following files

Loading the files please wait ....