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

devly-example

v2.7.0

Published

As a micro-services application grows, so does the need for a clear, coherent, and easy way to manage the set-up processes of all the components that make up the application.

Downloads

4

Readme

Introduction

As a micro-services application grows, so does the need for a clear, coherent, and easy way to manage the set-up processes of all the components that make up the application.

Existing Solutions

Two existing solutions to this problem involve containers and virtual machines. For a comparison between the two, checkout Pete Brey's article: https://blog.netapp.com/blogs/containers-vs-vms/

The Devly Solution

Devly is neither a containerization nor a virtual machine solution. It is a command line utility made up of composeable plugins built on node and npm. Each plugin abstracts out the low-level details of an application's set-up process and rolls it into a cli command.

With Devly, developers can leverage the power of their host machine and avoid the complexities of mounting files and folders into guest operating systems.

Integrating Your First App Into Devly

Create a separate repo for your app set-up cli tool.

Initialize and Install Dependencies

  • Run npm init
  • Run npm install --save @devly/devly-store @devly/devly-cli winston redux

Create Directories and Files

├── cli
    ├── top-level-command-1
    ├── top-level-command-2
    ├── top-level-command-3
    └── index.js
├── manifests
    ├── plugin-1
    ├── plugin-2
    ├── plugin-3
    └── index.js
├── plugins
    ├── plugin-1
    ├── plugin-2
    ├── plugin-3
    └── index.js
└── index.js

manifests directory

Manifest files export a javascript object that serves as the initial state for the corresponding plugin.

plugins directory

The plugins directory consists of files that compose the manifest with the corresponding action creator which then gets dispatched to the devly store. Note it is recommened to use a barrel file to manage all of your apps plugins.

Make sure to install your plugin as a dependency first.

const {store} = require('@devly/devly-store');
const {addApacheConfig, addApacheCommands} = require('@devly/devly-apache/actions');
const {dispatch} = store;

require('@devly/devly-apache');

dispatch(addApacheConfig(require('./manifests/apache')));
dispatch(addApacheCommands());

Define and Install Your Root CLI Command

Update your package.json to include a bin object.

{
  ...,
  "bin": {
    "dev-test": "./index.js"
  },
  ...
}

Make sure ./index.js includes the hashbang at the top of the file; and requires ./plugins and ./cli barrels.

#!/usr/bin/env node

require('./plugins');
require('./cli');

Finally, run npm install -g from the project's root directory.

Devly Plugins and Utilities

All Devly plugins and utilities are published to npm under the @devly scope. For a full list, visit https://github.com/devlyjs.

Here is a partial list: