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

@ts.adligo.org/tests4j

v0.2.6

Published

A small portion of the Tests4j code implemented in Typescript directly.

Downloads

5

Readme

tests4j.ts.adligo.org

A small portion of the Tests4j code implemented in Typescript directly.

Install with npm as usual;

npm install @ts.adligo.org/tests4j --save-dev

Import Into Your Code

import {ApiTrial, AssertionContext, Test, TrialSuite} from '@ts.adligo.org/tests4j'

Note the convention is a tests project with slinks, but can be anywhere.

Write your first TrialSuite, ApiTrial and Test

console.log('starting tests');
new TrialSuite('Your TrialSuite Name',[
  new ApiTrial('Your ApiTrial Name', [
    new Test('testSomething',(ac) => {
      console.log('in testSomething');    
      as.isTrue(false,'This should be True!');  
    })
  ])
]).run();
console.log('tests finished');

Test this Project, Compile and Deploy;

Run the local tests

 npm run test

Run the TypeScript Compile (creates a bin and dist folder)

 npm run tsc

Deploy

This command deploys, after you have logged in to https://registry.npmjs.org/;

npm publish --access public