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

sambac-webpack

v2.3.2

Published

Run your jasmine specs in the browser

Downloads

30

Readme

sambac

Run your Jasmine specs in the browser.

Requirements

  • webpack 2-4
  • jasmine

Setup

  1. yarn add sambac-webpack --dev (or npm install)
  2. Add a normal webpack configuration to your project. This conifguration should contain whatever loaders/rules/plugins are needed to run your tests. The entry point should be a string or an array of strings with globs that match all of your spec files, as relative paths from the root directory. See an example.

To Run

Make a package.json script with sambac --webpackConfig PATH_TO_CONFIG

A tab will open up in your browser with a list of specs to run. Clicking the links will open up tabs that run the specs and show the results every time that file or its dependencies change.

If you click the debug link, the loaded tab will not refresh automatically on file saving. The sourcemaps will refresh every time you refresh tbe browser though.

Command line options

--port 1234 The port the server runs on which displays the list of specs to run (default: 5678)

--webpackPort 1235 The port the webpack dev server runs on (default: 5679)

--showPath set to show path instead of only filename for specs

--disableRandom do not run specs in random order (the default since jasmine 3)

Node API

If you need to run sambac with the node API:

const sambac = require('sambac-webpack');
sambac({
  webpackConfig: PATH
  port: port,
  webpackPort: webpackPort,
  showPath: false,
  disableRandom: true
});

all of the options have the same defaults as the command line.

Configuration options

To customize sambac, add a sambac property to your webpack config

  sambac: {
    includePaths: ['/node_modules/babel-polyfill/dist/polyfill.min.js'],
    pattern: /spec$/
  }
includePaths

These files will be included in the generated bundles for each spec.

pattern (default: /.*\bspec\b.*/i)

If test-runners are inadvertently being created for included files, change this regex to filter them out.