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

pn_arc

v0.1.2

Published

pn_arcs is nothing more then just a ez discord.js bot commands creator. It is creted to make my and my friends life easier 😂

Downloads

1

Readme

Welcome to Noah King's pn_arcs 👋


About

pn_arcs is nothing more then just a ez discord.js bot commands creator. It is creted to make my and my friends life easier 😂.

  • Load Discord bot Templet
  • Create a command file

Installation

install the package globally

$ npm i -g pn_arcs
$ p_arcs
$ nstart

What each package does

  • [pn_arcs] - Load a simple command handler Bot
  • [nstart] - Create a command file

pn_arcs

Start by opning your terminal and run p_arcs

? Bot name: Arc
? Bot prefix: ? //you can go into your .env file and change it
? Your bot `TOKEN` please: My_Token //you can go into your .env file and change it
Installing dependencies...

Creates folder with command/event/handlers


nstart

Start by cdinto your command file and run nstart

? Command name: noahdance
? Command description: Noah cant Dance
? What is your client called: Arc

    Success! Created noahdance at `C:\Prohacker\Github\Noah/`noahdance

Creates your command file


  module.exports = {
    name: 'noahdance', //name of your command
    description: "Noah cant Dance",//description of what your command does
     run: async (Arc, message, args) => {
        
    }
}
  

For People using Replit

Replit doesn't allow you to install the package globally so you will need to require pn_start if you wish to create command files and the same with pn_arcs to load simple command handler bot.

const {pn_start,pn_arcs,Log} = require('pn_arcs')

Log() //log does nothing more then just console.log("Im Ready")
//if you wish to create command file use pn_start 

pn_start()

!!Reminder to remove pn_start from your index.js after you created your command file. You can require it again if you wish to create an another comamnd file

For People using <Vs Code> as your platform

No need to use this Package

JavaScript has something call User Snippets where you can make it so it loades your command/code. Go to Manage/Settings > User Snippets > and JavaScript.

{
// Place your snippets for javascript here. Each snippet is defined under a snippet name and has a prefix, body and 
	// description. The prefix is what is used to trigger the snippet and the body will be expanded and inserted. Possible variables are:
	// $1, $2 for tab stops, $0 for the final cursor position, and ${1:label}, ${2:another} for placeholders. Placeholders with the 
	// same ids are connected.
	// Example:
	// "Print to console": {
	// 	"prefix": "log",
	// 	"body": [
	// 		"console.log('$1');",
	// 		"$2"
	// 	],
	// 	"description": "Log output to console"
	// }
}