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

node-strap

v1.1.0

Published

Traversing through any directory to initialize/export in one swift move.

Downloads

9

Readme

Node-Strap

A simple utility function to help bootstrap Node.js projects.

Usage

The simplest way to use it would be.

const nodeStrap = require('node-strap');

nodeStarp('./initializers');

And that's it. The function will navigate to the directory. Find all files with the extension .js and require them.

requiring a function If node-strap will require a function it will call that function immediately. Keep that in mind, if you want to supply some arguments to that function use options.applyArgs

Options

node-strap supports an options as a second argument:

  • rootDir - tells the function the root directory of your project. If not specified it will use process.cwd() to determine this value. Therefore it is a good idea to add this option, a simple __dirname should be good enough :wink:
  • applyArgs - a list of arguments to supply to a function if one was required, default: []
  • strapDirectories - flag that tells if node-strap require files in a directory if it encountered one, default false. If this is set to true, then keep in mind that callOrder doesn't support setting up for multiple directories, only 1 array can be specified.
  • callOrder - an array of files data will determine the order of required files, default: []. The extension .js can be omitted, for example:
const callOrder = ['first_file.js', 'second_file.js'];
// or
const callOrder = ['first_file', 'second_file'];

Either way is fine. And yes, I'm aware that I've redfined a const value, it's just to show that you should pick one :smirk:

  • strapFirst - this one is a bit tricky, but in short, you can specify only few list of files that will be "bootstrapped" first, and the rest will be required as read in directory (most likley aplhabetically, but that's not guaranteed). Important is that, options.callOrder takes precedense, if it is specified, this option will be ignored.

Caveat

The exported function is synchronous. Please keep that in mind. The use case for this was to initiate a project, so you wouldn't have to write all those require by hand. Just keep them in one place. And require is synchronous therefore I've seen no reason to make it asynchronous :sunglasses: