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

node-aria-tools

v2.1.0

Published

NAT stands for - NodeJS - Aria - Tools

Downloads

31

Readme

NAT

NAT stands for

  • NodeJS
  • Aria
  • Tools

Requirements

  • NodeJS 16

Philosophy

Actions are segmented and are not run unless needed. This allows for faster compilation when needed.

Usage

First Run

Make sure to download the certificates locally. Paste them in ~/.m2/keystore. You must have a cert.pem and a private_key.pem.

nat --init

Will install vrotsc, vropkg and vrotest globally for you... you can specify different version of btva by passing --btvaVersion=2.35.0

General

nat -b -p

This will be all you need... (TEMP)it will do mvn clean package if the target folder does not exists, since for now it still depends on it for dependencies (TEMP)

Tests

nat -t

This will test the code. You must have built it beforehand (or you can add -b to the command).

Performance

Watch Mode

In one terminal:

nat --watch --watchMs 1000

Will build the code and start recompiling only the changed file.

in a separate terminal you can run nat -p to push the code when it completes or even nat -t to run unit tests

Roadmap

  • [x] Better Certificate Handling. Certificates should only work with local paths.
  • [x] Better vrotsc/vropkg installation
  • [x] More Customizability regarding inputs
  • [x] Don't rely on initial mvn clean package
  • [x] Building Code
  • [x] Compiling Code
  • [x] Convert information about the artifact to a special lock file.
  • [x] Pushing code
  • [x] Running Tests
  • [x] Save Artifact in memory so we don't read it twice
  • [x] Improve Push Code Logic
  • [x] Only push changed files for watch mode?
  • [x] Download dependencies
  • [x] Definitions
  • [ ] Code Coverage
  • [ ] Push Dependencies
  • [ ] Don't rely on vrotsc, vropkg and vrotest from maven central

Development

Setting Up BTVA Dependencies

  • Follow the instructrions for the first run.
  • run npm run dev in one terminal first
  • run tsc --watch in one terminal and keep it running