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

@ferstack/libuilderjs

v5.1.1

Published

A simple library builder

Downloads

10

Readme

LiBuilderJs

While developing a library it can be real painful to write the index file manually, having to write code and then export the export in the index file each time.

I wrote this script to automate the process of writing the index file, it recursively reads all files inside a given directory and generates an index file.

Configuration

The script should be configured under .libuilderrc.js file, here are the possible options for it:

// .libuilderrc.js

/** @type {import('libuilderjs').Config} */
const config = {
  src: string, // will watch files inside this directory
  dist: string, // will write the index file to this directory
  additional_code?: string, // path to the additional code file
  defaultTags?: "private" | "public", // public by default
};

export default config;

Usage

Mostly

The mostly key is set to public by default, which means that all files under src will be exported in the index file, unless you add //private to the file start, in this case the file will not be exported. But if you set it to private, then all files will be private unless you add //public to the file start.

This is useful when you want to export more files than you want to hide.

Additional code

The additional_code key is used to add additional code to the index file, for example, if you want to add a global import to all files, you can add it to the additional_code file and it will be added to the index file.

Contributing

I plan to add more features to this script, as an array of directories for src, but for now it's just a simple script that does the job. If you have any ideas or suggestions, feel free to open an issue or a pull request.