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

@nichoth/tap-ssc

v0.6.8

Published

Run tests in a browser environment from the command line

Downloads

928

Readme

tap ssc

tests Socket Badge semantic versioning license

Run tests in a browser environment from the command line.

The interface is inspired by tape-run. Just pipe some JS into the tap-ssc command, and your tests will run in a browser environment.

Instead of electron, a dependency of tape-run, this uses @socketsupply/socket to create a browser-like environment.

install

npm i -D @nichoth/tap-ssc

use

Bundle your client side JS, then pipe it into this tool, which is installed as the tap-ssc command.

Your tests will be running in a browser environment, but all tap output will go to the terminal.

Use it as a part of package.json scripts:

"scripts": {
    "test": "esbuild --bundle test/index.js | tap-ssc"
},

Or on the command line:

npx esbuild --bundle test/index.js | npx tap-ssc

example

// example/test/index.js
import { test } from '@nichoth/tapzero'

test('browser environment', t => {
    t.ok(window, 'window should exist')
})

Then in the terminal:

npx esbuild --bundle test/index.js | npx tap-ssc

see this example

pass in your own html file

[!NOTE]
This is in progress.

Use command line argument --html=filename.html

esbuild --bundle --platform=browser --format=esm test/html.js | tap-ssc --html=test.html | tap-arc

In your html, be sure to include a script tag pointing at bundle.js:

<script charset="utf-8" src="bundle.js" type="module"></script>

This is useful if your application code depends on another file that you are linking to via HTML, eg

<head>
    <meta charset="UTF-8">
    <title>tests</title>
    <script src="https://example.com/my-js-dependency/dist/index.umd.min.js"></script>
</head>
<body>
    <script src="bundle.js"></script>
</body>

how does this work?

We build an ssc binary once after you install this package

The package binary, ./cli.js, takes javascript that is piped to stdin, and writes it to a file at the right location -- target + /bundle.js. Then it runs the ssc binary and pipes the output to stdout.

test this module

This will use the example directory to install this as a dependency, then run a given test.

A passing test

npm test | npx tap-arc

A failing test

npm run test-fail

A test that throws an error

npm run test-err