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

rijs.export

v0.0.9

Published

[![Coverage Status](https://coveralls.io/repos/rijs/export/badge.svg?branch=master&service=github)](https://coveralls.io/github/rijs/export?branch=master) [![Build Status](https://travis-ci.org/rijs/export.svg)](https://travis-ci.org/rijs/export)

Downloads

13

Readme

Ripple | Export

Coverage Status Build Status

Combines all resources under the resources directory into a single index.js file. This is so you can export and import a bundle of resources from separate repos by simplying requireing them. Note that this is not the same bundling, since function resources are linked with requires, such that you could subsequently browserify the output (index.js) to produce a client bundle.

import buttons from 'ux-button'
import inputs from 'ux-input'
import rijs from 'rijs'

ripple = rijs({ .. })
  .resource(buttons)
  .resource(inputs)

Running rijs.export (defaults to rijs.export dist/resources), likely as part of a npm run build would place the index.js file under dist/resources/index.js. You then just need to point the main field in your package.json to point this file so it can be required.