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

threax-npm-tk

v6.0.0

Published

This project provides a build system for the front end for Threax Hypermedia Framework projects. It enables the use of artifacts.json files to describe what to publish for a project. It also supports the other commands the framework makes use of like tsim

Downloads

19

Readme

threax-npm-tk

This project provides a build system for the front end for Threax Hypermedia Framework projects. It enables the use of artifacts.json files to describe what to publish for a project. It also supports the other commands the framework makes use of like tsimport or clean. It is written in typescript and compiles to javascript.

Installing

Globally

Ideally install this as a global package.

Run npm install -g threax-npm-tk to install.

You probably also want typescript npm install -g typescript.

Project

You can also install the toolkit in your project by adding threax-npm-tk to devDependencies in the package.json file in your repo. This will then override any calls to threax-npm-tk to your locally installed copy. While backward compatibility is a big part of the toolkit this can help you fix a problematic program that can't be updated right away. However, due to bloat in the node_modules directory this should be avoided if possible.

Running

Run the program with threax-npm-tk here are the example tasks from a framework project:

"build": "threax-npm-tk build && dotnet bundle",
"clean": "threax-npm-tk clean",
"trash-modules": "threax-npm-tk clean -o node_modules",
"import-tsconfig": "threax-npm-tk tsconfig"

Artifacts.json

This file describes how to copy files in a project. A typical project comes with a file that looks like the following:

[
  {
    "typescript": {
      "compile": true
    }
  },
  {
    "pathBase": "Client",
    "outDir": ".",
    "copy": [
      "Client/Images/*"
    ]
  }
]

This tells the artifacts system to build the local typescript config and to copy any images from the Client/Images folder. This only describes the resources for the current project. For other modules each npm package will have an artifacts.json file that is scanned for during build. The combined output of all of these files will be written to the output directories. This makes it easy to pull in dependencies without needing to modify a ton of config files.

Development

Building

To build run tsc in the root directory. This will update all the javascript files.

Running Local Copy

To test the local results run node .\run.js to run the program.