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

component-as-module

v0.3.0

Published

Require components from node programs

Downloads

14

Readme

component-as-module

It allows to require components from node modules as well as share them with npm community.

Examples

Require stand-alone component (with all dependencies in a components dir):

var component = require('component-as-module')
var min = component('component-min')

Add additional lookup paths or enable dev dependencies:

var boot = component('boot', function(loader) {
  loader.addLookup('node_modules')
  loader.development()
})

Alternative way to require components is to create a special require function:

var req = component.createRequire(function (loader) {
  loader.addLookup('components')
})

var min = req('component-min')

This differs from the above examples in that all loaded components are preserved between calls, so, for example, requiring component-min second time is fast and you recieve the same instance.

Sharing components with npm

To make a component consumable with npm:

  1. Create a package.json file

  2. Set the name field to either full or partial component name, i.e. to username-foo or to foo.

  3. List dependencies. Because npm understands github urls you can safely specify them in a component style:

{
  "name": "foo",
  "dependencies": {
    "bar": "org/bar",
    "baz": "org/baz",
    "qux": "*" // dependency from npm (assuming it is a component) is also ok.
  }
}
  1. Create a node specific main file:

node-main.js

module.exports = require('component-as-module')(__dirname)

package.json

{
  "name": "foo",
  "dependencies": {
    "bar": "org/bar",
    "baz": "org/baz",
    "qux": "*", // dependency from npm (assuming it is a component) is also ok.
    "component-as-module": "*" // add additional component-as-module dependency
  },
  "main": "node-main"
}

After that you can safely publish it to npm. It will work like any other npm module. (Just don't forget to include component.json to package.)

Why

I believe there should be only one package convention for the web. No matter what side it is. Component is a good one. This project should help to use it for both node and browser.

Installation

with npm

npm install component-as-module

To run tests

npm install -d
npm test

License

MIT