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

mark-tested-specs

v1.2.0

Published

Add comments in your tests and check your md specs

Downloads

1

Readme

mark-tested-specs - EXPERIMENTAL

NPM package TypeScript Eslint Prettier

Getting Started

This CLI library helps you mark the specifications that were tested in a markdown file.

How to Use

  1. First, you need to install mark-tested-specs as a development or global dependency. You can do this using your preferred package manager:
npm install --global mark-tested-specs
npm install mark-tested-specs --save-dev
yarn add -D mark-tested-specs
pnpm install mark-tested-specs --save-dev
  1. Then create a script in your package.json
{
  "scripts": {
    "update:marks": "mark-tested-specs -d ./src/ -s ./src/example.md "
  }
}
  1. About parameters
  • **-d ** (required) The path where you will indicate that a specification was tested, it can be in a comment in your typings or in your specs
  • -s (required) This is your file that contains your specifications, this file will be updated as you complete the specifications
  1. For this to work, your spec file will have to have a syntax similar to this [](#any-mark-name#), example:
###Var

'Var' is test

update me [](#any-mark-name#)

| Name     | Type                  |                         |
| -------- | --------------------- | ----------------------- |
| text     | String                | [](#any-mark-name#)     |
| location | [Location](#location) | [✅](#any-mark-name#)   |
| location | [Location](#location) | [❌](#any-mark-name#)   |
| location | [Location](#location) | [❌](#any-mark-name-2#) |

And to make a mark updated, simply write test #any-mark-name# in one of your files specified with -d, example

it('should test #any-mark-name#', () => {
  // blah blah blah
});

After running the command with "npm run update:marks" that we defined in package.json, all markers found with "test #any-mark-name#" will be marked as ✅, example:

### Var

'Var' is test

update me [✅](#any-mark-name#)

| Name     | Type                  |                         |
| -------- | --------------------- | ----------------------- |
| text     | String                | [](#any-mark-name#)     |
| location | [Location](#location) | [✅](#any-mark-name#)   |
| location | [Location](#location) | [✅](#any-mark-name#)   |
| location | [Location](#location) | [❌](#any-mark-name-2#) |
  1. You can use this however you want, but by giving a suggestion, you can integrate this at the end of your tests
{
  "scripts": {
    "jest": "jest && npm run update:marks",
    "update:marks": "mark-tested-specs -d ./src/ -s ./src/example.md "
  }
}

Contributing to the project

Would you like to contribute to the project? Excellent! In our contributing.md guide, you'll find information on how to create a Pull Request, code standards we follow, and how to report bugs. Your contribution is valuable and will help improve the tool for everyone.

I hope these explanations and examples are clear and useful!

Known issues

To report issues, if possible, please provide a snippet or link to the code on GitHub where the issue can be replicated. You can report issues here.

You can make suggestions here

Next steps

...