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

niagara-test-server

v0.1.14

Published

HTTP server for testing Niagara web applications

Downloads

816

Readme

niagara-test-server

A tiny little HTTP server for use in Niagara unit testing. It knows how to do a couple things.

moduledev

It can read your moduledev.properties file, receive web requests for Niagara module assets, and retrieve those files from their corresponding moduledev locations. In most cases this won't be needed, since a test station will be running in moduledev mode. In the case that your unit tests can't start a station, but still need to reference Javascript files in other modules, use moduledev.

To make use of this, proxy requests for myStation:stationPort/module/ through to myServer:testServerPort/module/.

test globals

Add some globals in the server config:

globals: {
  hello: 'world',
  foo: 'bar'
}

Then require niagara-test-server/globals via RequireJS. It will give you a global testGlobals object:

console.log(window.testGlobals.hello); //'world'
console.log(window.testGlobals.foo); //'bar'

Mostly useful when adding these to your Grunt config. When requiring niagara-test-server/public/karmaUtils you'll magically get some special behavior when you pass in certain globals:

  • testOnly - a regex string. Only specs that match this will be run.
  • testNever - a regex string. Specs that match this will never be run.

static files

It can also serve up files that are located inside the module itself. Put them in the /public/ folder. Standard test utility files like logging into the station should go here.

For instance, /public/browserLogin.js is accessible at myServer:testServerPort/public/browserLogin.js.

If you need it to do something else, you can pass it a ghetto-middleware listener to receive other web requests as well.

It's useful for unit testing Niagara web apps.

Example

var config = {
  moduleDevFilePath: 'd:/niagara/r40/niagara_home/etc/moduledev.properties',
  host: '127.0.0.1',
  port: 8091,
  globals: {
    testOnly: '^myModule'
  }
};

var server = require('niagara-test-server');

server.start(config, function (err, server) {
  if (err) {
    return;
  }
  
  // server is http.Server
  console.log('server started');
});