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

@scriba/completion

v1.0.4

Published

AI-powered auto-completion for web-based text/code editors.

Downloads

2

Readme

About

Code Naming Guidelines

This document provides a comprehensive set of guidelines for writing clear, easily navigable, and collaborative code. It focuses on the naming and categorization of files and modules, which are crucial for communicating their scope and function. Adhering to these conventions ensures the code remains modular, readable, and accessible.

Identifying Modules (Folders & Files)

Since this project is a public npm package, it is important to maintain a clear distinction between public and private modules.

We use the $ and _$ prefix naming conventions to distinguish between public and private modules. This applies to both folders and individual file modules. The presence of these prefixes indicates the module's scope and its ability to be imported.

  • A _$ prefix signifies a private module for internal use only. It can only be imported or used within its own domain.

  • A $ prefix denotes a public module that is accessible to a broader range. These modules can be imported or used by the end-user.

In cases where a module is a folder, it is not mandatory to have an index.ts code-barrel file. However, it is recommended to include one. This allows for the use of the import * as $SubModule from '$Module/$SubModule' syntax, which can enhance code readability and maintainability.

Identifying Public Exports (Files & Methods)

We use the [ use ] useCamelCase prefix in file names and useCamelCase prefix in method names to indicate single files/functions that are meant to be imported by other modules. The presence of this prefix signifies that the method or function is an exported entity, ready for import by other modules.

Identifying Private Exports (Files & Folders)

A file or folder without any of the previously mentioned prefixes is considered part of the internal logic of the current module. These entities are not meant for import by modules or files outside the current directory (../), thereby maintaining a private scope of functionality. This classification helps in preserving the code's integrity and prevents unintended access or modifications.