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

find-at

v1.2.2

Published

cli, search files

Downloads

1

Readme

Program CLI for searching files by pattern

Description

Within the framework of this project, a utility has been implemented to search for a file (s) in a specified directory.

Install:

npm install -g find-at

Utility features:

  • Search all file(s) in all directories
  • Search all files in all directories, except not need
  • Search for specific file
  • Report generation in the form of plain text

Instruction:

The utility takes three parameters <dir> <pattern> [ignore]

  • <dir> - Required arguments. The path to the directory in which the search is performed.
  • <pattern> - Required arguments. The template to be searched for, for example: src/**/*.ts
  • [ignore] - Optional arguments. The name of the file to exclude from the search

Usage example:

$ search node_modules @babel/generator/**/*.js index.js
File "buffer.js" was here: "node_modules/@babel/generator/lib"
File "base.js" was here: "node_modules/@babel/generator/lib/generators"
File "classes.js" was here: "node_modules/@babel/generator/lib/generators"
File "expressions.js" was here: "node_modules/@babel/generator/lib/generators"
File "flow.js" was here: "node_modules/@babel/generator/lib/generators"
File "jsx.js" was here: "node_modules/@babel/generator/lib/generators"
File "methods.js" was here: "node_modules/@babel/generator/lib/generators"
File "modules.js" was here: "node_modules/@babel/generator/lib/generators"
File "statements.js" was here: "node_modules/@babel/generator/lib/generators"

Attention:

If get an error zsh: no matches found: , when you enter a template type `src/example/**/*.js``, something that would get rid of her type in the console setopt +o nomatch. More info here here.

Video instruction:

asciicast