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 🙏

© 2025 – Pkg Stats / Ryan Hefner

filespec

v0.2.0

Published

File-based Testing Library for JavaScript/TypeScript

Readme

FileSpec

FileSpec is a File-based testing library for JavaScript/TypeScript.

Installation

npm install -D filespec

Workflow

To use FileSpec you can create testing files ending with any of the following patterns: *.spec.ts, *.spec.js, *.test.ts, *.test.js. They can be located anywhere in your project but it's recommented to put them next to the source files being tested.

For example, suppose you have a src directory with a routes.ts file, you can create a routes.spec.ts file and execute the tests with the filespec src command.

Writing Tests

Each test file must export an array containing all the tests, even if you only have one. The general structure is as follows:

// feature.spec.ts file
export default [
  "Feature Description",

  Test => {
    return Test('Test Description', assertion)
  }
]

You can have one description for all the test as the first element of the array, this is useful to distinguish between several files since it's the first thing shown in the test results.

The rest of the array is any number of functions that take another function as argument and return the application of that function with a test description and the assertion, which must have a boolean value; if this value is true then the test is marked as successful, otherwise it's marked as failed.

You can name the test functions as you like, but keeping it as Test can be a good convention to follow.

The following is a another example of a test file:

// routes.spec.ts file
export default [
  "Server Routes",

  Test => {
    const route = '/'
    const actual = getRouteMessage(route)

    return Test('Single Test Description',
      actual === 'Hello World!'
    )
  },

  Test => {
    return Test('A single test', true)
  },

  myOtherTest => {
    return MyOtherTest('A custom-named test', true)
  }
]

Executing the filespec <projectDir> command will run those tests and return the results.

Usage with TypeScript

You can run TypeScript files using the ts-node package. First install it as a development dependency:

npm install -D ts-node

And then run the FileSpec command with it:

ts-node node_modules/filespec/dist/bin <projectDir>

This is necessary because embedding the TypeScript compiler in FileSpec and making it work is not trivial when the tests have dependencies. If you know a simple solution for this where we don't need to manually resolve the dependencies please open an issue and let me know.

Licence

MIT License - James Kolce