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

@momsfriendlydevco/lawyers.txt

v1.0.0

Published

Lawyers.txt file generation

Downloads

19

Readme

@MomsFriendlyDevCo/Lawyers.txt

Simple Supabase like lawyers.txt generation for easy inclusion within projects.

This project exports a single string which can be glued into static files when generated.

It can also be run as lawyers from any project its installed in:

import {dirName} from '@momsfriendlydevco/es6'; // Or work out where we are somehow
import lawyers from '@momsfriendlydevco/lawyers.txt';

let lawyersSpeil = await lawyers({
    path: dirName(),
});

// ...Do something with the string

Auto generation within a Vite project

The following is an example of how to generate + output a lawyers.txt file using vite-plugin-inject NPM:

// Within vite.config.js
import {dirName} from '@momsfriendlydevco/es6';
import pluginInject from 'vite-plugin-inject';
import lawyers from '@momsfriendlydevco/lawyers.txt';

export default {
    plugins: [
        pluginInject([
            /* ... other plugin config ... */
            {
                name: 'lawyers.txt',
                async content() {
                    return await lawyer({
                        path: dirName(),
                    });
                },
            },
        ])
    ],
}

Example Output

Lawyers.txt
-----------
For compliance.

If you're a creator/contributor to one of these packages, thanks!

Last Updated: 2024-03-14

# Package Name License Version                 Repository
- ------------ ------- ----------------------- ----------------------------------------
1 list-it      MIT     1.3.12                  https://github.com/takamin/list-it
2 nlf          MIT     2.1.1                   http://github.com/iandotkelly/nlf
3 node-getopt  MIT     0.3.3-forked-by-takamin https://github.com/jiangmiao/node-getopt

API

lawyers(options)

This project exports a single function which takes the root path to scan from and some additional options. It returns a promise which resolves to a String when generation has completed.

Supported options are:

| Option | Type | Default | Description | |---------------|-----------------|-----------------|------------------------------------------------| | path | String | process.cwd() | The path to start scanning from | | exclude | Array |[] | Array of packages to exclude, by name | |excludeSelf|true |true | Exclude the named package in the starting path | |depth |Number |1 | Package depth to scan | |production |Boolean |true` | Only show production level packages |