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

eprint

v0.1.2

Published

Run your script in Electron and print to terminal

Downloads

10

Readme

Eprint

For when you want to run a script in the browser - without opening a browser, and print something of value to the terminal. Why would you ever need to do that? In my case I needed to run various benchmarks in the browser and somehow output the result to the terminal. Reason why it is called Eprint is because we're utilizing Electron under the hood.

How to use

First install in your project.

npm install --save-dev eprint

Call eprint and eprintKill in your script (Note that both are global functions).

// do some computation
eprint('my script result')
// when script finished execution, call eprintKill to quit
eprintKill()

If you are using TypeScript, include this file in your source so that TypeScript won't complain.

// eprint.d.ts
export {}

declare global {
  var eprint: (str: string) => void
  var eprintKill: () => void
}

Compile your script and call it with eprint to execute and print result to terminal.

npm run build && npx eprint dist/my-script.js

You'll probably want to add a script to package.json for convenience.

  "scripts": {
    ...
    "benchmark": "npm run build-benchmark && eprint dist/benchmark.js"
  }

If you want to open developer tools for debugging, add --debug flag:

npm run build && npx eprint --debug dist/my-script.js

Reference

eprint

Print given string to the terminal. You can replace console.log with this function. Only caveat is it won't automatically print object so maybe call JSON.stringify prior.

eprintKill

Take no argument. Call this function when your script finished execution to stop Eprint process.