Download the PHP package sterlingdesign/css-cli without Composer

On this page you can find all versions of the php package sterlingdesign/css-cli. 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 css-cli

css-cli

This package is still in experimental stages

This is a Command line interface for automating the process of running CSS Development Tools. It is specifically meant for use with a Sterling Full Stack Framework directory structure, however it could be used to accomodate any directory structure using additional command line arguments.

The typical development cycle when developing custom CSS with SASS is:

  1. Edit the *.scss files located in one directory
  2. Run a Sass processor to produce the CSS output files (usually output to another directory)
  3. Run a tool against the generated CSS to add or remove vendor prefixes to support the target browsers
  4. Run a tool to clean whitespace and formatting, and either generate expanded CSS (for development) or compressed CSS (for production)

This utility automates these tasks.

At the time of this development, many of the best tools for accomplishing these tasks are written using JavaScript and are often implemented as plug-ins for tool chain utilities such as gulp. This utility takes advantage of some of those tools by leveraging the multi-threaded capabilities of PHP and shelling out to the various JavaScript tools which run under a separate node process. Also, in order to take advantage of the most up-to-date and most complete implementation of SASS, this interface makes use of the compiled Dart SASS processor which also runs in a separate process. Finally, the css-cli implements a shell-like interpreter which can accept commands that change the output characteristics of the CSS generated.

All versions of css-cli with dependencies

PHP Build Version
Package Version
Requires php Version >=7.1
ext-mbstring Version *
ext-parallel Version *
sevenecks/ansi Version ^1.0
ulrichsg/getopt-php 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 sterlingdesign/css-cli contains the following files

Loading the files please wait ....