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

require-main

v0.1.1

Published

Load the project's main script simply

Downloads

889

Readme

require-main

NPM version Build Status Dependency Status devDependency Status

A Node module to load the main script of your project simply

Overview

require-main is useful for developing npm modules. When we write a test for a npm module, usually we should load the module itself with require() by specifying the main script path explicitly, as below:

var yourLib = require('./'); // Or, something like "../lib/runner.js"

assert(yourLib, 'Your module is loaded.');

Instead of such a hard coding, we can use require-main to load the main module easily.

var yourLib = require('require-main')();

assert(yourLib, 'Your module is loaded.');

require-main offers the following advantages:

  • It keeps your test code simple even if your test directory has a complicated structure.
  • It prevents your package.json from having a wrong main field.
    • require-main() throws an error if there is no script files in the main path.

Installation

Install with npm. (Make sure you have installed Node.)

npm install --save-dev require-main

Usage

var requireMain = require('require-main');
var yourLib = requireMain();

Or, even shorter:

var yourLib = require('require-main')();

requireMain() returns the main module of the first package.json in the __dirname directory or the nearest parent directory.

If the package.json has no main field, requireMain() tries to load index.js in the current working directory.

License

Copyright (c) 2014 Shinnosuke Watanabe

Licensed under the MIT LIcense.