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 🙏

© 2025 – Pkg Stats / Ryan Hefner

cispacempt

v0.0.6

Published

Fast, open-source, local-and-cloud, CI/CD by CodespaceMPT.

Readme

CodespaceMPT CI

CodespaceMPT CI (CISpaceMPT) is a fast, efficient, and scalable Continuous Integration (CI) server that automates the execution of scripts in various stages of your CI pipeline. It is designed to integrate seamlessly with your repository, run defined commands, and log detailed results.

Installation

How It Works

CI Script Structure

Your CI pipeline is defined in a JSON-based script. Each CI script contains several stages, each with its own set of commands to run. Below is an example of how to structure the CI script:

{
  "stages": {
    "build": {
      "scripts": [
        "npm install",
        "npm run build"
      ]
    },
    "test": {
      "scripts": [
        "npm test"
      ]
    }
  }
}
  • stages: Defines the different stages of the CI pipeline.
  • scripts: Lists the commands to be executed in each stage.

Execution Flow

  1. Clone Repository: The CI server clones the repository and checks out the required branch.
  2. Parse Directory: The file system of the repository is recursively traversed (excluding node_modules), capturing the directory structure and content.
  3. Stage Execution: For each stage defined in the CI script, the server executes the specified commands sequentially.
  4. Log Results: The output (stdout, stderr) from each command is captured and logged along with any errors and exit codes.
  5. Time Tracking: The duration of the CI process is calculated and logged.
  6. Clean-up: Once the pipeline is complete, temporary directories are deleted.

Example Usage

Here’s how you can use the parse function to execute a CI script:

const ci = require('cispacempt');

// Sample CI script
const ciScript = {
  stages: {
    "build": {
      scripts: [
        "npm install",
        "npm run build"
      ]
    },
    "test": {
      scripts: [
        "npm test"
      ]
    }
  }
};

// Repository name
const repoName = "my-repo";

// File system content to be used during execution
const fileSystem = {/* your repository's file system in a json */};

ci.parse(ciScript, repoName, fileSystem, true)
  .then(result => {
    console.log("CI Log Result:", result);
  })
  .catch(err => {
    console.error("CI process failed:", err);
  });

Output

The parse function returns an object containing the CI process result:

{
  "output": "CI logs for each stage",
  "timestamp": "2025-04-14 12:00:00",
  "fileSys": { /* Parsed file system after ci */ },
  "ci_duration": "10.23",  // Duration in seconds
  "exitCode": 0  // Exit code (0 for success, non-zero for failure)
}
  • output: Logs from each stage.
  • timestamp: The timestamp of when the CI process was run.
  • fileSys: A JSON object representing the repository’s file structure.
  • ci_duration: Total time taken for the CI process (in seconds).
  • exitCode: The exit code from the final stage (0 if all commands succeed).

Clean-Up

After the execution, temporary directories are automatically cleaned up to save disk space.

License

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