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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@imprion91/finding-files

v1.1.2

Published

Looking which file is used in a page? With this library, you'll have a complete list of each files used by the current page.

Downloads

7

Readme

finding-files

CI npm version License: MIT

A simple and efficient npm library for finding files in a webpage.

Installation

npm install @imprion91/finding-files

or with yarn:

yarn add @imprion91/finding-files

Usage

Import ES Modules

import { FileFinder, createFileFinder, findAllFiles } from '@imprion91/finding-files';
import type { FileInfo, FindFilesOptions } from '@imprion91/finding-files';

// Example usage
const finder = new FileFinder({
    includeImages: true,
    includeCSS: true,
    includeJS: true,
});

finder.findFiles().then((files) => {
    console.log('All files:', files);

    // Filter only CSS files
    const cssFiles = finder.filterByType(files, 'css');
    console.log('CSS files:', cssFiles);

    // Group files by type
    const grouped = finder.groupByType(files);
    console.log('Grouped by type:', grouped);

    // Count total files
    const total = finder.countFiles(files);
    console.log('Total files:', total);
});

Import CommonJS

const { FileFinder, createFileFinder, findAllFiles } = require('@imprion91/finding-files');

Development

Prerequisites

  • Node.js >= 18.0.0
  • npm or yarn

Install dependencies

npm install

Available scripts

# Run tests
npm test

# Run tests with coverage
npm run test:coverage

# Run the linter
npm run lint

# Format the code
npm run format

# Check TypeScript types
npm run typecheck

# Build the library
npm run build

Project structure

finding-files/
├── tests/
│   └── FileFinder.test.ts
├── src/
│   ├── core
│   │   ├── FileFinder.ts    # Main class for finding files
│   ├── types
│   │   ├── index.ts         # Type definitions
│   └── index.ts             # Entry point for the library
├── dist/               # Compiled files (generated)
├── .github/
│   └── workflows/
│       └── ci.yml      # Configuration CI/CD
├── package.json
├── tsconfig.json       # Configuration TypeScript
├── .eslintrc.cjs       # Configuration ESLint
├── .prettierrc         # Configuration Prettier
└── jest.config.js      # Configuration Jest

Contributing

Contributions are welcome! Feel free to:

  1. Fork the project
  2. Create a branch for your feature (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

Contribution guidelines

  • Ensure all tests pass
  • Follow the code style (use npm run lint and npm run format)
  • Add tests for any new features
  • Update the documentation if necessary

License

This project is licensed under the MIT License. See the LICENSE file for details.

Acknowledgments

  • Thanks to all contributors

Created with love by MarquesThomasCoding, HosenMohsen, and Roland-HUON