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

@virtru/nanotdf

v0.0.1-beta.17

Published

## ⚠️ Warning

Downloads

4

Readme

NanoTDF

⚠️ Warning

This library is in continual development. The current implementation of NanoTDF library is as follows, but expect issues.

  • [x] Parse binary
    • [x] happy paths
    • [ ] sad paths
    • [ ] 80% code coverage
  • [ ] Decrypt nanoTDF
  • [ ] Encrypt nanoTDF
  • [ ] Encode binary

Build

The nanoTDF library will build two version. The difference between these version is slight, but significant.

  • Node /build
  • Browser /build-browser

To build run:

npm i
npm run build

Testing

There are three significant tests:

  • Node unit tests, located /src/**/*.test.ts
  • Node functional tests, located /tests/*.test.ts
  • Browser functional tests, located /tests/*.test-browser.js

To run the node unit tests and functional tests:

npm i
npm run test

To run the browser functional tests:

npm i
npm run build
open ./tests/browser-tests/index.html

Adding tests

Node tests:

  • Keep unit tests along side the scripts /src/**/<scriptName>.test.ts
  • Keep functional tests within /tests and give it a meaningful name

Browser tests:

  • Keep functional tests within /tests/browser-tests and give it a meaningful name
  • Add helpers to /tests/browser-tests/helpers.js
  • Add fixtures to /tests/browser-tests/fixtures.js as const fixtures_myNewFixture = {};
  • Add test to the /tests/browser-tests/index.html within the test comments boundary