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

file-concat-tool

v1.0.8

Published

A tool for generating context windows for AI prompting by recursively searching for .ts and .tsx files and concatenating their contents into a text file.

Downloads

97

Readme

File Concat Tool 🚀

npm
Weekly Downloads
License
Open Issues
PRs Welcome
Chalk used

Automated code context generator for AI prompting. Recursively combines source files (.ts, .tsx, .js, .jsx, .html, .css, .scss) while ignoring common non-source directories and files, and formats console output with colors.

🚨 Current Limitations

Supported File Types: .ts, .tsx, .js, .jsx, .html, .css, .scss
Excluded Patterns:

  • node_modules directory
  • Files containing "config" in name
  • Test directories (__tests__) and files (*.test.*)
  • Output file automatically added to Git exclude (.git/info/exclude)

Future updates may include additional file types and customization options.

💡 Motivation

Tired of manually copying code for AI prompts? This tool solves:

  • Automatic Git-exclude management 🔒
  • Smart test file exclusion 🧪
  • Recursive directory scanning 🔍
  • Clean, colored console output 📄

Get complete code context with one command!

🛠 Installation

Install globally via npm:

npm install -g file-concat-tool

🚦 Usage

  1. Navigate to your project:
    cd /path/to/your/project
  2. Run the tool:
    file-concat

Output: Creates source_files_content.txt with:

  • Tool credit header
  • Relative file paths
  • File contents separated by clear markers
  • Colored console log of processed files
  • Automatic Git exclude update

📁 File Processing Rules

| Status | Pattern | Examples | Action Taken | | ------ | -------------------------- | ---------------------------- | --------------------------- | | ✅ | All supported extensions | index.ts, style.scss | Included in output | | 🚫 | node_modules directory | Any nested dependency | Skipped entirely | | 🚫 | Files containing "config" | config.ts, app.config.js | Excluded from processing | | 🚫 | Test-related files | *.test.ts, __tests__ | Ignored during scan | | ⚠️ | Existing Git exclude entry | .git/info/exclude | Appended or already present |

🌟 Example Output

=== File: src/index.ts ===
import App from './App';

=== File: src/App.tsx ===
export default function App() { ... }

=== File: src/styles/main.scss ===
body { margin: 0; }

🤝 Contributing

We welcome contributions! Please follow our workflow:

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

📄 License

MIT Licensed - See LICENSE for details.


Made with ❤️ by noluyorAbi - Automate All The Annoying Things! 🤖