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

@carbondigital/robots-parser

v0.0.13

Published

Robots parser that is used in our SEO application.

Readme

Contributors Forks Stargazers Issues

About The Project

We wanted a tool internally that would help us rapidly scale our SEO efforts, but ultimately, give us the ability to migrate offf our current toolchain for SEO. Like many agencies, our team spent thousands on SEO-realted software each year. Since we're not a multi-million dollar agency, it always hurts to pay those bills.

In light of that, we are building this software initially for our own team. We have already seen the power of competing with well-known tools that currently exist. One thing we aim to achieve is more honesty and more transparency. This is why we are building some modules has open-source NPM packages. So, give all developers the ability to see exactly what we're doing and contribute if they desire.

Built With

Below are the major frameworks/libraries that are currently used in this project, or soon to be added in a future release.

Usage

Console.Log your robots.txt file:

import { robotsParser } from '@carbondigital/robots-parser';
robotsParser('console', './my-robots-file.txt');

Logged Output:

Sitemap: https://carbondigital.us/sitemaps/post-sitemap1.xml
Sitemap: https://carbondigital.us/sitemaps/page-sitemap1.xml
Sitemap: https://carbondigital.us/sitemaps/projects-sitemap1.xml
Sitemap: https://carbondigital.us/sitemaps/services-sitemap1.xml
Sitemap: https://carbondigital.us/sitemaps/locations-sitemap1.xml
Sitemap: https://carbondigital.us/sitemaps/category-sitemap1.xml

User-agent: SemrushBot
    Disallow: /
User-agent: SemrushBot-SA
    Disallow: /
User-agent: MJ12bot
    Disallow: /
User-agent: Mediapartners-Google
    Disallow:
User-agent: Googlebot-Image
    Disallow:
User-agent: *
    Disallow: /wp-admin/
    Allow: /wp-admin/admin-ajax.php

Return Array of data from your robots.txt file:

import { robotsParser } from '@carbondigital/robots-parser';
robotsParser('browser', './my-robots-file.txt');

Array Output:

[
  {
    type: 'sitemap',
    content: 'https://carbondigital.us/sitemaps/post-sitemap1.xml'
  },
  {
    type: 'sitemap',
    content: 'https://carbondigital.us/sitemaps/page-sitemap1.xml'
  },
  {
    type: 'sitemap',
    content: 'https://carbondigital.us/sitemaps/projects-sitemap1.xml'
  },
  {
    type: 'sitemap',
    content: 'https://carbondigital.us/sitemaps/services-sitemap1.xml'
  },
  {
    type: 'sitemap',
    content: 'https://carbondigital.us/sitemaps/locations-sitemap1.xml'
  },
  {
    type: 'sitemap',
    content: 'https://carbondigital.us/sitemaps/category-sitemap1.xml'
  },
  { type: 'blank', content: '' },
  { type: 'user-agent', content: 'SemrushBot' },
  { type: 'disallow', content: ' /' },
  { type: 'user-agent', content: 'SemrushBot-SA' },
  { type: 'disallow', content: ' /' },
  { type: 'user-agent', content: 'MJ12bot' },
  { type: 'disallow', content: ' /' },
  { type: 'user-agent', content: 'Mediapartners-Google' },
  { type: 'disallow', content: '' },
  { type: 'user-agent', content: 'Googlebot-Image' },
  { type: 'disallow', content: '' },
  { type: 'user-agent', content: '*' },
  { type: 'disallow', content: ' /wp-admin/' },
  { type: 'allow', content: ' /wp-admin/admin-ajax.php' }
];

Our SEM Links app is a Nest.js project. In that project, we have a data wrapper so all returned data is part of a "data" object. When testing this in Postman, here is the same data being returned.

{
  "data": [
    {
      "type": "sitemap",
      "content": "https://carbondigital.us/sitemaps/post-sitemap1.xml"
    },
    {
      "type": "sitemap",
      "content": "https://carbondigital.us/sitemaps/page-sitemap1.xml"
    },
    {
      "type": "sitemap",
      "content": "https://carbondigital.us/sitemaps/projects-sitemap1.xml"
    },
    {
      "type": "sitemap",
      "content": "https://carbondigital.us/sitemaps/services-sitemap1.xml"
    },
    {
      "type": "sitemap",
      "content": "https://carbondigital.us/sitemaps/locations-sitemap1.xml"
    },
    {
      "type": "sitemap",
      "content": "https://carbondigital.us/sitemaps/category-sitemap1.xml"
    },
    {
      "type": "blank",
      "content": ""
    },
    {
      "type": "user-agent",
      "content": "SemrushBot"
    },
    {
      "type": "disallow",
      "content": "/"
    },
    {
      "type": "user-agent",
      "content": "SemrushBot-SA"
    },
    {
      "type": "disallow",
      "content": "/"
    },
    {
      "type": "user-agent",
      "content": "MJ12bot"
    },
    {
      "type": "disallow",
      "content": "/"
    },
    {
      "type": "user-agent",
      "content": "Mediapartners-Google"
    },
    {
      "type": "disallow",
      "content": ""
    },
    {
      "type": "user-agent",
      "content": "Googlebot-Image"
    },
    {
      "type": "disallow",
      "content": ""
    },
    {
      "type": "user-agent",
      "content": "*"
    },
    {
      "type": "disallow",
      "content": "/wp-admin/"
    },
    {
      "type": "allow",
      "content": "/wp-admin/admin-ajax.php"
    }
  ]
}

Roadmap

We've got a simple setup on Canny. You can submit either a Github issue, or a Canny feature request for the SEM Links tool.

Contributing

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again! See contributing.md for more details.

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

Acknowledgments

Without these people and tools, life would be too complicated.