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

@irontitan/next

v2.3.2

Published

File template and cli helper for files using irontitan architecture

Downloads

14

Readme

Next

Fast creation of projects, files and domains in our Architecture

Build Status

Summary

Installation

Install it globally using your preferred package manager:

npm i -g @irontitan/next

Or

yarn global add @irontitan/next

Or

pnpm i -g @irontitan/next

Global options

Some options can be used through all commands (except help):

  • --dir <path>: By default, next runs on process.cwd(). If this option is provided, then the current working directory will be changed to path and all operations will be performed under this location

Usage

Next is aliased in your shell as next.

$ next <command> [options]

Commands

init

Creates a new project from scratch in a new folder with project-name as name. This command will create the structure defined here (to be translated) so all the docs about it is right there.

$ next init <project-name>

Options

This command accepts the Global options and:

  • --domains: A comma-separated list of domain names to be created along with the project. The names can be cased whatever you want, but they cannot contain spaces

Example: $ next init my-project --domains production-order,tag,userReport,user,inventory_report,userbackups

new

Work in progress

release

Work in progress

TODO

  • [ ] Create new command, it'll include the creation logic for several assets (events, domains, repositories, services, clients, errors, configs)
  • [ ] Create deploy command so we can create tags and deploys
  • [ ] Add --type option to the init command in order to create libs and other smaller projects
  • [ ] Update this doc
  • [ ] Improve code style and make things reusable
  • [ ] Translate architecture document to english