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

hot-pockets

v0.3.1

Published

Little hot-loading pockets of javascript

Downloads

16

Readme

hot-pockets

Hot-loading with zero build tools.

const hp = require('hot-pockets')

const elem = document.createElement('div')
document.body.appendChild(elem) 

const state = {
  counter: 0
}

hp(() => {
  // When you change something inside the hot-pocket, the code
  // is executed live with no page refresh.
  
  // When you change something outside the hot-pocket the page
  // automatically reloads.
  
  state.counter += 1
  elem.innerHTML = `This pocket has run ${state.counter} times since the last page refresh`
  elem.style.color = 'red'
})

Pure modules

If no hot-pockets instructions are found in a module it is considered a "pure" module, and the whole thing will be hot-loaded.

When you save changes to a pure module, any hp(() => { ... }) that uses it will be re-executed with the new code.

Ignoring modules

If you know a module causes side-effects, but you don't want to create a hot-pocket, you can tell hot-pockets to ignore the module by placing //@hp:ignore at the top.

Status

Working, but still experimental.

At the moment it's only working in electron but there's a pretty clear path forward if we want to port it to browser.

Suggestions Welcome! :)

Check out the example.