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

@gooddata/grunt-grizzly

v3.1.1

Published

Simple GoodData proxy server for client development.

Downloads

976

Readme

Grizzly

Simple GoodData proxy server for client development.

Usage

CLI

$ yarn add grunt-grizzly
$ yarn grizzly -h
Usage: grizzly -b [backend] -p [port] -d [document-root]

Options:
  -p, --port            local port to listen on           [default: 8443]
  -h, --help            show this help
  -b, --backend         backend host name                 [default: "secure.gooddata.com"]
  -d, --document-root   document root directory to use
  -s, --stub            stub file or function
  -c, --cert            path cert file
  -k, --key             path to key file
  -a, --autoassignPort  increment port number and if specified port is already in use

Direct with grunt

To run grizzly as a standalone server, the only thing you need to do is to run:

grunt

from root directory of grunt-grizzly.

As a grunt task

This module registers grizzly grunt task, so you can add

grunt.task.loadNpmTasks('grunt-grizzly');
grunt.task.run('grizzly');

to your gruntfile.

Configuration

grizzly task provides following configuration options:

  • backend host name of proxy endpoint Defaults to secure.gooddata.com.

  • host alias of backend

  • port number of local port to listen to. Defaults to 8443

  • root root directory, relative to project root. Default is base.

  • dir alias of root

  • cert path to certificate to use. Defaults to <grunt-grizzly>/cert/server.crt. You will hardly ever need to change this value.

  • key path to ssl key to use. Defaults to <grunt-grizzly>/cert/server.key. You will hardly ever need to change this value.

  • keepAlive This is not an option, it is a flag!!! If set, e.g. by calling

      grunt.task.run('grizzly:keepAlive');

    then grizzly will not exit after the server has been started. This is useful when starting standalone grizzly with no grunt tasks after grizzly task. If not specified, grunt will execute next task normally.

  • stub express instance setup function/module that is called with an instance of express app before setting up the static root directory handler.

    Form: function or path to file that exports a function, i.e.

      module.exports = function(app) {
      	// do something with app here
      }
  • quiet This is not an option, it is a flag!!! If set, grizzly will not produce any output (i.e. will not log anything to console).

Testing

There are no integration tests so far. Unit tests are stored under test/unit/cases and can be run with grunt test. Jasmine is used.