npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

grunt-jison-processor

v0.1.1

Published

Parse files based on grammars, generate standalone parsers, or both.

Downloads

2

Readme

grunt-jison-processor

Parse files based on grammars, generate standalone parsers, or both.

Getting Started

This plugin requires Grunt ~0.4.5

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-jison-processor --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-jison-processor');

The "jison-processor" task

Overview

In your project's Gruntfile, add a section named jison-processor to the data object passed into grunt.initConfig().

grunt.initConfig({
  'jison-processor': {
    options: {
      // Global options go here.
    },
    target: {
      options: {
        // Task-specific options go here.
      },
      files: {
        dest: [ src ]
      }
    }
  }
});

Options

options.debug

Type: boolean Default: false

If set to true, displays information about the parser.

options.grammar

Type: object|string Mandatory

The grammar that defines the parser. It may include a lexical grammar and can contain EBNF.

If it's a object, it is a grammar JSON representation used by Jison. If it's a string, it contains either a JSON grammar, a Jison grammar, or a path to a file that contains either a JSON or Jison grammar.

More information on http://zaach.github.io/jison/docs/#specifying-a-language

options.lexer

Type: object|string

If defined, overrides the lexical grammar included in options.grammar, if any.

The format is the same as for options.grammar.

options.name

Type: string Default: parser

The name of the parser variable. Useful only when options.output is defined and options.type is js.

options.output

Type: string

If defined, saves the parser to this file.

options.parser

Type: string Default: lalr

The algorithm to use for the parser. Possible values are lalr, ll, lr, lr0, and slr.

options.type

Type: string Default: commonjs

The type of module generated. Possible values are amd, commonjs, and js. Useful only when options.output is defined.

Files

files is an object where keys are a destination and values are sources.

If the sources consist of a single file, its content is parsed and the result is written in the file destination

If the sources consist of several files, their content is parsed and the results are written in the directory destination, the files have the same name as their corresponding source.

If there are no sources, the destination is skipped and nothing is generated.

Usage example

In this example, the target calculator processes each file in the directory test/calculator and saves them in the directory tmp/calculator. It also saves the parser in the file tmp/calculator-parser.js.

The calculator grammar is adapted from an example from Jison.

grunt.initConfig({
	'jison-processor': {
		calculator: {
			options: {
				output: 'tmp/calculator-parser.js',
				grammar: 'test/calculator.json'
				// grammar: 'test/calculator.jison'
				// grammar: require('./test/calculator.js')
			},
			files: {
				'tmp/calculator': 'test/calculator/*'
			}
		}
	}
});

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

0.1.1

  • add more tests
  • polish documentation

0.1.0

  • grunt-jison-processor is born \o/
  • processes files based on grammar
  • optionally generates standalone parsers