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 🙏

© 2026 – Pkg Stats / Ryan Hefner

architect-init

v1.0.2

Published

CLI tool to help you start a new Architect app by creating all the structure and main files.

Readme

architect-init

CLI tool to help you start a new Architect app by creating all the structure and main files of your plugins.

Install

npm install -g architect-init

Plugins

Before running architect-init you must create a config file containing your plugins list.

It's a simple text file with each plugins on a new line.

Example :

firstplugin
firstplugin.secondplugin
thirdplugin
thirdplugin/fourthplugin

With default options (auto structure), this will create the following directory structure :

lib
├─ firstplugin
├─ firstplugin.secondplugin
└─ thirdplugin
    └─ fourthplugin

Run

New project

architect-init new

It will then ask you the following questions :

  • Where is stored your plugins list file ?

    Specify the path to your plugins list file created above. Default : plugins.conf

  • Where do you want to store the plugins ?

    The directory where to store plugins. Default : lib/

  • Do you want sub or dotted dirs for plugins ?

    • auto : keep the structure of your plugins.conf file (default)
    • sub : force subdirs for "sub" plugins
    • dotted : force dotted dirs for "sub" plugins
  • Create package.json file for each plugins (yes|no) ?

    Create a default package.json file in each of the created folders. Template of the package.json file is located in tpl/package.json. Default : yes

  • Create main file for each plugins (yes|no) ?

    Create a main JS file in each of the created folders. Template of the main file is located in tpl/main.js. Default : yes

  • Force the creation of files even if they exists (yes|no) ?

    Do you want to replace existing (package.json/main) files in directories ? Default : no

New plugin

architect-init generate <pluginName>

Directory structures

Here is the final structure of plugins with options :

auto

lib
├─ firstplugin
├─ firstplugin.secondplugin
└─ thirdplugin
    └─ fourthplugin

sub

lib
├─ firstplugin
│   └─ secondplugin
└─ thirdplugin
    └─ fourthplugin

dotted

lib
├─ firstplugin
├─ firstplugin.secondplugin
├─ thirdplugin
└─ thirdplugin.fourthplugin

TODO

  • Create tests

Licence

The MIT License (MIT)

Copyright (c) 2013 Leeroy Brun

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.