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

@coli.codes/naming

v0.0.34

Published

- variable naming - route naming - entity naming - file naming - directory naming

Downloads

115

Readme

Coli Naming

  • variable naming
  • route naming
  • entity naming
  • file naming
  • directory naming

Installation & Usage

yarn add @coli.codes/naming
import { nameit } from "@coli.codes/nameit";

nameit("Content Wrap"); // - [ContentWrap, contentWrap, content-wrap, content_wrap, CONTENT_WRAP, contentwrap]

// of course, you can pass the configurations.

Scope handling

with ScopedNamer you can pervent confliction of each identifiers' name

conflict prevent prefix/suffix

  • +n - [conflicting-name-0, conflicting-name-1]
  • +hash - [conflicting-name-GT3, conflicting-name-AG9]
  • +named entity (not recommanded) - [conflicting-name-white, conflicting-name-ambient]
  • +single conflicting underscore escape - [conflicting_name, _conflicting_name or __conflicting_name]

Exceptional realworld scenarios (supported)

nextjs' page route naming

  • [slug].js
  • _app.js

Usecases

  • const Wrapper = styled.div~;
  • interface IModel {}
  • class Model {}
  • function add () {}
  • function Component () {}
  • pages/[slug].js
  • const _memberVar = calc(porps.value)
  • const API_SECRET = "alza0000"
  • function checkIfThatIsTrue() : boolean
  • const isSomethingTrue : boolean

Input scenario

/ is a seperator, it can be replaced with cases - 'a/b' -> "AB", "aB", "a_b", "_a_b", etc..

  • "+-$" - "plus/minus/dollarsign"
  • "- Dollar" - "_/dollar"
  • "Hi" - "hi"
  • "Content wrap" - "content/wrap"
  • "" - "unnamed/rand()"
  • "" - ""
  • "$" - "dollarsign" ($ is a valid name is es, but not a good pattern, you have to specify it as a sign keyword in order to use it - see it below)
  • Unique.dollarsign - "$"