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

@jurei733/responses

v1.0.1

Published

Data interfaces for processing assessment data.

Downloads

2

Readme

License: CC BY-SA 4.0 npm

This package contains of type definitions for processing assessment data. Additionally, you find TypeScript interfaces and classes, so these data structures can be used in a coherent way.

JSON Schema

The definitions are available as JSON schema files. This way, you can validate your data. The schema files are also the source of documentation: See here to learn about the data structures.

There is one data structure specified by Verona Interfaces: variable list. In this repository responses, you find a class to handle variable info of this structure, but the specification is not part of this repo.

For developers

  • The data is defined via json schema documents. Every folder stands for one definition.
  • Every schema is validated against a number of json implementations. Validation is part of the CI, so an invalid schema will not lead to a new documentation. Add valid and invalid json implementations!
  • The documentation is also part of the CI. Don't generate it manually!

Adding new spec

  1. Add new folder with new json schema
  2. Add valid and invalid tests.
  3. Add new script entry in package.json
  4. Add new script call in .gitlab-ci.yml to add the test to CI
  5. Add new operation in asyncapi.yaml to document the new spec.