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

chewie

v0.1.14

Published

Helper module for documentation independent generation concept.

Downloads

40

Readme

Build Status npm version npm npm dependencies

Chewie is a Node.js module that you can use in a skeleton build with any static site generator. It supports a different approach to documentation, unlike the single source publishing documentation trend. With Chewie, you can distribute your content in different locations, essentially making it distributed source publishing.

What does this mean in practice? Imagine your product consists of forty different documentation topics. Using Chewie, you can document them all in one portal using a static site generator, but keep the content in forty different repositories, each managed by different teams using git.

Table of contents

Installation

npm install chewie

Usage

Quick start

To use chewie with gulp.js, add the following to the gulp file:

const chewie = require('chewie');

Create documentation

sudo npm install -g jsdoc
jsdoc -r src -d documentation

Open index.html under apidocs/documentation

How to release

To release a Chewie project, run this command:

npm run release

Development

  • To run all the tests, use the following command:

    DOCU_PROVIDER=GIT NODE_ENV=master npm run test-unit && npm run test-integration
  • To run just one specific test, use one of the following commands:

    DOCU_PROVIDER=GIT NODE_ENV=master ./node_modules/mocha/bin/mocha --harmony_shipping test/unit/NAME_OF_THE_UNIT_TEST.spec.js
    DOCU_PROVIDER=GIT NODE_ENV=master ./node_modules/mocha/bin/mocha --timeout 40000 --harmony_shipping test/integration/NAME_OF_THE_INTEGRATION_TEST.spec.js

License

Copyright (c) 2014 SAP SE or an SAP affiliate company. All rights reserved.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License here: LICENSE

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Defects and feedback

To offer feedback or report issues, use the Github issue tracker.

Contribution

To learn how you can contribute to this project, see the CONTRIBUTING document.

Credits

YaaS

From your YaaS team.