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

@sprungg/code-mapper

v1.3.0

Published

JavaScript/TypeScript project structure analyzer

Downloads

31

Readme

@sprungg/code-mapper

Description

@sprungg/code-mapper is a JavaScript/TypeScript project structure analyzer that helps you visualize and understand the structure of your codebase. It analyzes file structures and Abstract Syntax Trees (ASTs) to provide insights into your project's architecture.

Features

  • Analyze JavaScript/TypeScript project structures
  • Visualize file and folder hierarchies
  • Detect and display import/export relationships
  • Generate project statistics

Installation

npm install @sprungg/code-mapper

Usage

Programmatic API

You can also use it programmatically in your Node.js applications:

import { mapProject, logStats } from '@sprungg/code-mapper';

async function analyzeProject() {
  const projectPath = './path/to/your/project';
  const graph = await mapProject(projectPath);
  logStats(graph, projectPath);
}

analyzeProject();

Output Example

When you run @sprungg/code-mapper, it generates a structured output of your project. Here's an example of what the output might look like:

The projectGraph object returned by mapProject is structured as follows:

{
  "nodes": [
    {
      "id": "src/index.ts",
      "type": "FILE",
      "name": "index.ts",
      "path": "src/index.ts",
      "metadata": {
        "extension": ".ts"
      }
    },
    {
      "id": "src/analyzers",
      "type": "FOLDER",
      "name": "analyzers",
      "path": "src/analyzers"
    }
  ],
  "relationships": [
    {
      "id": "rel-1",
      "type": "IMPORTS",
      "sourceId": "src/index.ts",
      "targetId": "src/analyzers/fileAnalyzer.ts"
    }
  ]
}

logStat formats the output to a more readable format:

=== Project Structure Analysis ===

📁 Files and Folders:
📂 src
📄 src/index.ts
📂 src/analyzers
📄 src/analyzers/fileAnalyzer.ts
📄 src/analyzers/astAnalyzer.ts

🔗 Dependencies:
src/index.ts → src/analyzers/fileAnalyzer.ts
src/index.ts → src/analyzers/astAnalyzer.ts

📊 Statistics:
Total Files: 3
Total Folders: 2
Total Import Dependencies: 2

CLI Usage

You can use code-mapper directly from the command line:

npx @sprungg/code-mapper [project-path] [format] [output-file]

Options:

  • project-path: Path to your project (default: current directory)
  • format: Output format - 'json' or 'text' (default: text)
  • output-file: Optional file path to save the output

Examples:

# Analyze current directory and display text output
npx @sprungg/code-mapper .

# Analyze specific directory and save JSON output
npx @sprungg/code-mapper ./my-project json output.json

# Analyze and save text output
npx @sprungg/code-mapper . text output.txt

CLI Usage with Git Plugin

The Git plugin can be enabled with various options:

# Basic usage with git information
npx @sprungg/code-mapper --git

# Exclude commit messages from git info
npx @sprungg/code-mapper --git-no-message

# Specify number of commits to include in history
npx @sprungg/code-mapper --git-history=5

# Combined with other options
npx @sprungg/code-mapper /path/to/project --git --format json -o output.json

Git plugin options:

  • --git: Enable git information collection
  • --git-no-message: Exclude commit messages from git info
  • --git-history=N: Include N most recent commits (default: 1)

Contributing

Contributions are welcome! Please read the CONTRIBUTING.md for guidelines on how to contribute to this project.

License

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

Contact

For any questions or feedback, please open an issue on GitHub.