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

gould

v1.3.0

Published

**Gould** is a super simple Node module to display your backend console logs on the frontend console. It works by the following steps:

Downloads

5

Readme

#Gould

Gould is a super simple Node module to display your backend console logs on the frontend console. It works by the following steps:

  1. Writing the backend logs to a file called 'temp.log'
  2. Establishing a socket connection with the frontend using 'socket.io'
  3. Utilizing the 'fs' module's 'watch' method to watch for every new log message
  4. Utilizing the 'fs' module's 'read' method to get each new log message from 'temp.log'
  5. Piping each of these messages to the front end socket
  6. Console logging the messages once they arrive on the front end

The process is nearly simultaneous.

Setup is easy. On your backend app.js or server.js file, ensure you initialize a server using http:

const server = http.createServer(app);

On the front end of any page where you want simultaneous logging, simply include the following lines, switching out the appropriate localhost port or remote URL as needed:

<script src="https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.7.2/socket.io.min.js"> </script>
<script type="text/javascript">
    let socket = io.connect('http://localhost:3000');
    socket.on('stuff', function (data) {
      console.log(data);
    });
</script>

That's it. You're done.

Notes: Gould must be required after server instantiated This is for express