Download the PHP package webignition/node-jslint-output-parser without Composer

On this page you can find all versions of the php package webignition/node-jslint-output-parser. 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 webignition/node-jslint-output-parser

Informations about the package node-jslint-output-parser

node-jslint-output-parser Build Status

Overview

PHP parser for the output of reid/node-jslint, get lovely things such as:

If you're building a PHP-based application that programmatically interfaces with node-jslint, this is for you.

Usage

The "Hello World" example

Running JSLint from the command line through node-jslint can give you a nice collection of error information to process:

Let's parse that in a unit test and see what we can get:

See? Useful. We can see how many entries are in the output, what the entries are and how much of the linted content was scanned.

Seeing Why JSLint Stopped Scanning

I LINT YOU. Y U NO SCAN ALL CODE

Sometimes JSLint encounters too many errors, sometimes it stops scanning if the code quality is just not up to scratch.

It's nice to see why scanning stopped.

Building

Using as a library in a project

If used as a dependency by another project, update that project's composer.json and update your dependencies.

"require": {
    "webignition/node-jslint-output-parser": "*"      
}

Developing

This project has external dependencies managed with composer. Get and install this first.

# Make a suitable project directory
mkdir ~/node-jslint-output-parser && cd ~/node-jslint-output-parser

# Clone repository
git clone [email protected]:webignition/node-jslint-output-parser.git.

# Retrieve/update dependencies
composer.phar install

Testing

Have look at the project on travis for the latest build status, or give the tests a go yourself.

cd ~/node-jslint-output-parser
phpunit

All versions of node-jslint-output-parser with dependencies

PHP Build Version
Package Version
Requires php Version >=5.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 webignition/node-jslint-output-parser contains the following files

Loading the files please wait ....