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

@ani-team/projentry

v0.1.0

Published

Projentry local server with sockets interaction to library module

Downloads

12

Readme

Projentry [Demo]

WIP: For a while work in progress. Because of it - use this solution carefully

More stable release would be after v1.0.0

npm npm npm bundle size Hits

GitHub commit activity

Assistant for your project

  • UI Dashboard
  • Code Driven Documentation
  • Tech debt monitoring
  • Project discovering
  • Maintaining and refinements of project knowledges

Motivation

There are a lot of typical problems of projects development

Onboarding

It takes specific time before your new project teammate could be useful for development. Yet more time for own initiatives.

Also, onboarding of any colleagues require resources from old teammates - that little bit slows down project development.

Fight with Legacy

Projects only get more complicated over time, and it becomes more difficult to monitor the quality of decisions made, compliance with the project conventions

Live Doc

Difficult to keep project documentation up to date Conventions, decisions made, concepts, backlog - it should all be quickly accessible

Project health

Sometimes there are not enough linters and toolkits to monitor the "health and condition of the project" - specific for your code and conventions

Not general issues, that are resolved by any other solutions

We wanted toolkit, that helps us to measure our unique tech debt by our conventions!

Overview

Our solution is UI Dashboard for:

  • Grouping and navigating by hude docsbase
  • Inspect and aggregate tech debt at one page
  • Packages discovering with info learning

Later will be available also:

  • our own lib usage
  • project scheme navigating
  • global search by docs
  • dark theme :D
  • and of course - more customizing of UI and lib logic!

Get started

  1. At first, install our npm package
    $ npm i @ani-team/projentry
  2. Then, specify config in any cosmicconfig format
    // .projentryrc.js
    module.exports = {
        docs: {
            getStarted: {
                paths: [
                    "/docs/get-started.md",
                ],
            }
            conventions: {
                paths: [
                    "/pages/readme.md",
                    "/features/readme.md",
                ],
            },
        }
        issues: {
            visibleLinesDelta: 3,
            types: [
                {
                    tag: "lowCoupling",
                    description: "Low coupling of modules. Will be resolved soon",
                    severity: 4,
                },
                {
                    tag: "dry",
                    description: "Repeat of logic. Take a closer look at using as some common using parts",
                    severity: 2,
                },
            ]
        }
    }
       
  3. And finally, specify and run projentry script for running dashboard
    // package.json
    "scripts": {
        ...
        "projentry:start": "projentry"
    },
    $ npm run projentry:start
  4. Profit! Now, any changes in your codebase, inner docs or config - would affect projentry dashboard

Further Reading