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

tinycoder

v202308.9.1

Published

Browser code editor that aims to be kept as simple as possible.

Downloads

2

Readme

tinycoder

Browser code editor that aims to be kept as simple as possible.- Short description

Ups and downs

Ups:

  1. Simple to get around
  2. Has a Tkinter-styled config API

Downs:

  1. More event-based than property-based
  2. Doesn't handle automatic indentation

Examples

Changing the configuration

tc = new tinycoder(document.getElementById("tc"))
tc.config("syntaxHighlight", false)
console.log(tc.config("syntaxHighlight")) // Output: false

On special circumstances...

tc = new tinycoder(document.getElementById("tc"))
tc.events.update(function(e) {
	console.log("Code is now updated!", e)
})
tc.updateCode("let it = \"go\"") // Output: Code is now updated! {code: "let it = \"go\""}
// On user edit, the "update" event will not be fired.
// Use "edit" instead.

Documentation

For your ease, the documentation is given right here where are you watching this right now.

Events

|Name|Sample object|Fired on| |:-:|-|-| |update|{"code": "let it = \"go\";"}|Code updated programmatically via updateCode()| |edit|{"code": "let it = \"go\";", "code": false}|Code edited programmatically via updateCode() and by user| |focus|{"code": "let it = \"go\";"}|focus-like event| |unfocus|{"code": "let it = \"go\";"}|blur-like event| |any|Any from above|After every event|

Configuration keys

|Name|Sample value|Description| |:-:|:-:|-| |syntaxHighlight|true|Enables/disables syntax highlighting| |lineNumbers|true|Enables/disables line numbers| |fontStr|"normal 12px \"Cascadia Mono\""|More information|