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

js-editor-tags

v0.1.5

Published

Generate ctags file based on code analysis

Downloads

45

Readme

js-editor-tags Build Status

Generate tags file for javascript codebase using static code analyses.

Is it fast?

Yes, it is fast.

Usage

npm install -g js-editor-tags

# generate `tags` file for all _not git ignored_, _existing_, js/mjs/jsx files in the current folder and subfolders
js-editor-tags

# update existing `tags` file instead of regenerating it
js-editor-tags -u

# generate `tags` file and keep it up to date as the files change
js-editor-tags -w

# if you keep compiled js in git, you might want to exlude it
js-editor-tags --ignore "dist" --ignore "build"

# ultimately, you can just pipe in a list of files to tag
git ls-files | js-editor-tags

# and watch it your way
fswatch -0 -r . | while read -d "" file_path; do git ls-files $file_path; done | js-editor-tags -u

Another option is to use a git hook to run the script. Here's an example.

Running tests

yarn test