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 🙏

© 2025 – Pkg Stats / Ryan Hefner

synk-js

v2.1.0

Published

Companion to the go synk package

Downloads

30

Readme

synk-js

Classes for connecting to a synk server.

Entry Point Options

  • main: 'dist/synk.js' transpiled to umd - node 8 uses main
  • module: 'src/index.js' es6 classes with 'import' statements

Using the module entry point

Import statements looks like this:

import './Connection'; // looks for ./Connection.es6.js

Your resolver needs to expect the .es6.js extension. Webpack offers an easy solution.

Webpack Example

Note that client code that uses webpack will probably want to use a webpack rule like the one below:

  // We need to add .es6.js to import resolution.
  resolve: {
    extensions: [".js", ".json", ".es6.js"]
  },
  module: {
    rules: [
      // Compile client es6. Only needed if host module needs to compile es6.
      {
        test: /\.js$/,
        exclude: /(node_modules|bower_components)/,
        use: {
          loader: 'babel-loader',
        }
      },
      // If we encounter a .es6.js file in node_modules, babel it. This is
      // required for host modules that use the 'module' entrypoint.
      {
        test: /node_modules.*\.es6\.js$/,
        use: {
          loader: 'babel-loader'
        }
      }
    ]
  },