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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@hobbyfarm-org/guacamole-common-js

v1.6.0

Published

Guacamole Common JS (ESM-bundled from Maven, with named + default exports)

Readme

guacamole-common-js

This repository tracks the official guacamole-common-js release on Maven and periodically builds a tree-shakable ECMAScript module from it. The tracking works semi-automatically with renovate bot.

Overview

The goal of this project is to fetch the latest release of the Apache Guacamole Common JS library from Maven Central, convert it into an ES module with named exports, and publish it as an npm package. This way we allow modern bundlers to "tree shake" for smaller bundle sizes.

The project is split into two main parts:

  • Build Scripts: Located in the scripts/ directory. These scripts are responsible for downloading, unzipping, transforming, testing and rebuilding the Guacamole source code.
  • GitHub Workflows: Located in the .github/workflows directory. This folder contains the following 3 jobs:
    • renovate-runner.yml: The job to run our renovate bot (once per month)
    • build.yml: The build job to build and test our bundled esm module on PRs
    • release.yml: A job which triggers a new release if changes were made to the VERSION const of our build-guacamole.js

Repository Structure

my-guac-repo/
├─ .github/
│   └─ workflows/
│       ├─ build.yml
│       ├─ release.yml
│       └─ renovate-runner.yml
│
├─ guac-dist/                 # not contained in this repo, but created if build-guacamole.js is run
│   ├─ dist/
│   │   └─ index.js           # final ESM build
│   ├─ README.md              # npm Readme (copied from main repo)
│   └─ package.json           # npm package metadata
│
├─ scripts/
│   ├─ node_modules/          # compiled dev dependencies
│   ├─ tests/
│   │   └─ test-exports.mjs   # file to test our npm package exports
│   ├─ build-guacamole.js     # file to build our npm package
│   ├─ package-lock.json
│   └─ package.json           # dev dependencies metadata
│
├─ LICENSE                    # Apache 2.0 License
├─ README.md                  # Main repo Readme
└─ renovate.json              # config for renovate bot

Building the package

cd scripts
npm run build-guacamole
  • Published Package: The final npm package is assembled in the guac-dist/ folder, containing:
    • A dist/ directory with the built ES module (index.js)
    • A package.json file configured for ES modules

Usage

To reference this package in your project as guacamole-common-js you can include it in your package.json the following way:

  "dependencies": {
    "guacamole-common-js": "npm:@hobbyfarm-org/guacamole-common@^1.5.5"
  },

This package is compatible with @types/guacamole-common-js. You can import this package in TypeScript the following way:

// Named imports (if you only need specific functionality):
import { Keyboard, Tunnel } from 'guacamole-common-js';

// Or, use the default export:
import Guacamole from 'guacamole-common-js';
const client = new Guacamole.Client(/* ... */);