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

madnessenjin

v1.3.2

Published

app development assistant

Downloads

159

Readme

Madness Enjin CLI v1.1.13

The Enjin is an application development assistant to make cross platform coding simpler and more fun. The enjin is meant to be completely opt-in, not required but will make your life easier.


Install

To install the enjin just run the command below in your terminal. Once you do, you will be able to use the new commands with the enjin command.

npm install -g madnessenjin


Commands

start

  • REPO - Link to git repo you are cloning (If using github you can use user/repo format)
  • NAME - The name of the application / folder
  • --EDITOR / -e - (Optional) The code editor to open your project in (code = VS Code, code-insiders = VS Code Insiders)
  • --REPO / -r - (Optional) The git remote repo you would like to make the origin

This will clone the repo and then run npm install for you. You can use short links for GitHub, like MadnessLabs/Animadness. You can also pass in credentials for private repos in the short link style using the convention, user:password@MadnessLabs/Animadness. The optional flags let you open your favorite code editor and hook your project to a git remote like Github with the same short linking.

Example:

enjin start <REPO> <NAME> -e [EDITOR] -r [REPO]

enjin start ionic-team/stencil-starter MyStencilApp -e code -r MyGithub/MyNewApp


add component (ac - for shorthand)

  • NAME - The name of the component (Must contain a -)
  • --PROPS / -p (Optional) - The props you wish to use inside your new component (Comma separated and : to set types)

Example:

enjin add component <NAME> -p [PROPS...]

enjin ac your-name -p first:string,last:string


remove component (rc - for shorthand)

  • NAME - The name of the component (Must contain a -)

This will create a new component folder with an SCSS and TSX file with props passed. It will read end edit your stencil.config.js as well.

Example:

enjin remove component <NAME>

enjin rc your-name


init

  • WITH [package / prompts] (Optional) - To create your enjin file with package or prompts

This will create an enjin.json in the current directory using either prompts or a package.json file.

Example:

enjin init [WITH]


env

  • [NAME] - The name of the environment

This will create an environment (enjin.[NAME].json) file in the directory.

Example:

enjin env [NAME]