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

tedit-build

v0.0.0

Published

A command-line utility that implements the tedit build system in node.

Downloads

3

Readme

tedit-compiler

A node module that implements the tedit build system.

This implements the same logic as found in tedit, but works with files on the filesystem and uses node instead of chrome APIs.

Installing this tool

Currently the best way to install this tool is to clone it recursivly and then npm link from the new directory.

git clone [email protected]:creationix/tedit-build.git
cd tedit-build
npm link

This will clone the tool and all it's dependencies using versions I know work.

If you prefer, you could install using npm directly, but that will pull the bleeding edge versions of all deps which might not work.

npm install -g git://github.com/creationix/tedit-build.git

Usage Example

For example, this tool can be used to build tedit from git without already having a copy of Tedit from the chrome store.

git clone [email protected]:creationix/tedit-app.git --recursive
tedit-build tedit-app out chrome-app filters

This will clone tedit and it's dependencies. Then tedit-build will import all these files into a local in-memory git database. It will then do a full export of the chrome-app subfolder using the filters subfolder for build rules. The built version of tedit will be available in the new out folder.

This can then be added to chrome using chrome://extensions.

TODO

Eventually this tool will be smarter and faster. I want to make it monitor for changes and do incremental builds. This way you can use sublime or your favorite text editor and still have full access to the tedit build system. Also I plan on adding a local server that serves a repo over HTTP same as Tedit can to.

Basically this tool has all the cool stuff from Tedit, but lets you continue to use your existing editor and tools.