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

elm-spec-runner

v2.5.1

Published

Node CLI for Elm-Spec

Downloads

6,670

Readme

elm-spec-runner

Node CLI for Elm-Spec

Install

$ npm install --save-dev elm-spec-runner

Usage

Use elm-spec-runner to run elm-spec suites from the command line.

$ elm-spec [options]

By default, elm-spec executes a spec suite in JSDOM. Note that while this is probably the fastest way to execute specs, JSDOM does have limitations. For example, JSDOM does not calculate layout positions for HTML elements, so any specs that describe layout in precise ways may fail unexpectedly.

For the most realistic execution environment, you should run specs in a real browser. To run your specs in Chromium, simply provide chromium (or another valid value) for the --browser option.

Note: elm-spec will result in a non-zero exit code if any observations are rejected or an error prevents the spec suite from running to completion.

Options

--elm -- Specify path to elm executable. Defaults to elm

--specRoot -- Specify the root directory for specs; should contain the elm.json file for the specs. Defaults to ./specs

--specs -- Specify a glob for spec modules, relative to specRoot. Defaults to ./**/*Spec.elm

--browser -- Specify the browser environment for the specs: jsdom, chromium, webkit, firefox, remote. If remote is selected, a URL will be provided; visit the URL to run the specs. Defaults to jsdom.

--visible -- Show the browser while the specs are running. Does nothing if the browser is jsdom or remote.

--watch -- Rerun the spec when files change in directories listed in the source-directories of your specs' elm.json file.

--parallel -- Run scenarios in parallel, up to the number of CPU cores. This can lower spec suite run time for larger spec suites. Does nothing if the browser is remote.

--endOnFailure -- Stop the spec suite run on the first failure.

--css -- Path to a CSS file to load in the browser, relative to the current directory. You may specify multiple css files.

--help -- Print options