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

gulp-gorilla

v0.1.0

Published

Compile gorillascript files

Downloads

5

Readme

status

Information

Usage

let gorilla = require 'gulp-gorilla'
require! gulp
let gutil = require 'gulp-util'

gulp.task 'gorilla', #
  gulp.src './src/*.gs'
    .pipe gorilla({ +bare }).on('error', gutil.log)
    .pipe gulp.dest './public/'

Error handling

gulp-gorilla will emit an error for cases such as invalid gorillascript syntax. If uncaught, the error will crash gulp.

You will need to attach a listener (i.e. .on('error')) for the error event emitted by gulp-gorilla:

let gorilla-stream = gorilla { +bare }

// Attach listener
gorilla-stream.on 'error', #(err)
  throw? err

In addition, you may utilize gulp-util's logging function:

let gutil = require 'gulp-util'

// ...

let gorilla-stream = gorilla { +bare }

// Attach listener
gorilla-stream.on 'error', gutil.log

Since .on(...) returns this, you can make you can compact it as inline code:


gulp.src './src/*.gs'
  .pipe gorilla({ +bare }).on('error', gutil.log)
  // ...

Options

// default options
let opt =
  bare: false
  source-map: false

Source maps

gulp-gorilla can be used in tandem with gulp-sourcemaps to generate source maps for the gorilla to javascript transition. You will need to initialize gulp-sourcemaps prior to running the gulp-gorilla compiler and write the source maps after.

let sourcemaps = require('gulp-sourcemaps');

gulp.src './src/*.gs'
  .pipe sourcemaps.init()
  .pipe gorilla({ +bare }).on('error', gutil.log)
  .pipe sourcemaps.write()
  .pipe './dest/js'

// will write the source maps inline in the compiled javascript files

By default, gulp-sourcemaps writes the source maps inline in the compiled javascript files. To write them to a separate file, specify a relative file path in the sourcemaps.write() function.

let sourcemaps = require('gulp-sourcemaps');

gulp.src './src/*.gs'
  .pipe sourcemaps.init()
  .pipe gorilla({ +bare }).on('error', gutil.log)
  .pipe sourcemaps.write './maps'
  .pipe './dest/js'

// will write the source maps to ./dest/js/maps

LICENSE

(MIT License)