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

nodewrite

v1.0.15

Published

NodeWrite: multi-domain website management for content networks.

Downloads

4

Readme

NodeWrite

Build Status Code Climate Coverage Status Dependency Status

Screenshot

Requirements

Installation

Clone respository to your system:

git clone https://github.com/nodewrite/nodewrite.git

Install package dependencies:

npm install --loglevel=error --depth=0

Configuration

After npm installation is complete a gulp task will the copy default configuration file for each installed plugin into the /config/default directory. You can change the values within default configuration files, but each package update will cause the defaults to be overwritten by the upgraded version.

To make configuration changes that are permanent you'll want to create a sub-directory within /config that targets your current NODE_ENV and store your settings there instead. The quickest way to do this is by duplicating the config/default directory. Optionally, you may add individual config files and settings as needed as opposed to duplicating all the defaults.

The configuration object loaded on startup is merged together such that the global config/default settings are loaded first followed by the merging of keys provided by an environment's custom config/[env] directory.

The example configuration provided below is targeting three different environments each with its own nodewrite-core-data settings. Plugin configuration options not provided by a custom environment are inherited from the defaults:

.
├── /config
|   ├── /default
|   |   ├── core-data.yml
|   |   ├── plugin-gravatar.yml
|   |   └── etc...
|   ├── /development
|   |   └── core-data.yml
|   └── /production
|   |   └── core-data.yml

If NODE_ENV is not set, but a config/development directory exists then it will be used automatically without the need to set your NODE_ENV to development.

API

Public events and methods provided by this package are outlined below.

Events

Events for this package are emitted on the nodewrite channel:

  • register - plugin was registered by the server with signature function(packageName) where:
    • packageName - package name of the plugin that was registered.