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

@bemedev/cli-test

v0.1.6

Published

A library for testing CLI libraries (INCEPTION !!)

Downloads

1

Readme

A library to test cli library (INCEPTION !!)

Install

npm

npm i @bemedev/cli-test

yarn

yarn add @bemedev/cli-test

pnpm

pnpm add @bemedev/cli-test

Usage - Describe

import { describe_cli } from '@bemedev/cli-test';

describe_cli('', ({ makeDir, writeFile, readFile, ls, mockFs }) => {
  test('#0 => No files', async () => {
    const files = await ls();
    expect(files).toEqual([]);
  });

  mockFs('writeFile');

  test('#1 => Create a folder "test"', async () => {
    return makeDir('test');
  });

  test('#2 => The folder "test" should be created', async () => {
    const files = await ls();
    expect(files).toEqual(['test']);
  });

  test('#3 => Create a file "test/test.txt"', async () => {
    return writeFile('test/test.txt', 'test');
  });

  test('#4 => The file "test/test.txt" should be created', async () => {
    const files1 = await ls();
    expect(files1).toEqual(['test']);

    const files2 = await ls('test');
    expect(files2).toEqual(['test.txt']);
  });

  test('#5 => Read the file "test/test.txt"', async () => {
    const content = await readFile('test/test.txt');
    expect(content).toEqual('test');
  });
});

Todo and Skip

import { describe_cli } from '@bemedev/cli-test';

describe_cli.todo('', () => {});
describe_cli.skip('', () => {});

RunIf

import { describe_cli } from '@bemedev/cli-test';

describe_cli.runIf(true)(
  '',
  ({ makeDir, writeFile, readFile, ls, mockFs }) => {
    test('#0 => No files', async () => {
      const files = await ls();
      expect(files).toEqual([]);
    });

    mockFs('writeFile');

    test('#1 => Create a folder "test"', async () => {
      return makeDir('test');
    });

    test('#2 => The folder "test" should be created', async () => {
      const files = await ls();
      expect(files).toEqual(['test']);
    });

    test('#3 => Create a file "test/test.txt"', async () => {
      return writeFile('test/test.txt', 'test');
    });

    test('#4 => The file "test/test.txt" should be created', async () => {
      const files1 = await ls();
      expect(files1).toEqual(['test']);

      const files2 = await ls('test');
      expect(files2).toEqual(['test.txt']);
    });

    test('#5 => Read the file "test/test.txt"', async () => {
      const content = await readFile('test/test.txt');
      expect(content).toEqual('test');
    });
  },
);

And so on...

Add on

To mock fs libraries, we have a cli that create a setup file for your vites config. You need to add an custom extension to your vite config "setupFs".

Incide your vitest.config.ts, example :

/** Here */ import { setupFs } from '@bemedev/cli-test/lib/extension';
import { aliasTs } from '@bemedev/vitest-alias';
import { exclude } from '@bemedev/vitest-cov-exclude';
import { defaultExclude, defineConfig } from 'vitest/config';

import tsconfig from './tsconfig.json';

export default defineConfig({
  plugins: [
    aliasTs(tsconfig as any),
    exclude(
      './src/cli/**/*',
      '**/index.ts',
      './src/helpers/partialMock.ts',
    ),
    /** Here */ setupFs(),
  ],
  test: {
    bail: 10,
    maxConcurrency: 10,
    passWithNoTests: true,
    slowTestThreshold: 3000,
    exclude: [
      ...defaultExclude,
      './src/cli/cli.pre.test.ts',
      './src/cli/cli.post.test.ts',
    ],
    coverage: {
      enabled: true,
      extension: 'ts',
      reportsDirectory: '.coverage',
      all: true,
      provider: 'v8',
    },
  },
});

N.B

Now our describe function is a ffully vitest compatible function, so you can use it with all vitest features.

N.B

In order to function, you need to add a peer dependencies : "cmd-ts" and eventually "vitest".