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

@homebridge/node-pty-prebuilt-multiarch

v0.11.14

Published

Fork pseudoterminals in Node.JS

Downloads

20,212

Readme

node-pty-prebuilt-multiarch

npm npm Prebuild Binaries Discord

This project is a parallel fork of node-pty providing prebuilt packages for certain Node.js and Electron versions.

Inspired by daviwil/node-pty-prebuilt.

Usage

Thanks to the excellent prebuild, prebuild-install modules, and prebuildify using this module is extremely easy. You merely have to change your node-pty dependency to @homebridge/node-pty-prebuilt-multiarch and then change any require statements in your code from require('node-pty') to require('@homebridge/node-pty-prebuilt-multiarch').

NOTE: We started shipping prebuilds as of node-pty version 0.8.1, no prior versions are provided! If you were using an earlier version of node-pty you will need to update your code to account for any API changes that may have occurred.

How It Works

We maintain a parallel fork of the node-pty codebase that will be updated as new releases are shipped. When we merge new updates to the code into the prebuilt-multiarch branch, new prebuilt packages for our supported Node.js and Electron versions are updated to the corresponding GitHub release.

When @homebridge/node-pty-prebuilt-multiarch is installed as a package dependency, the installation script checks to see if there's a prebuilt package on this repo for the OS, ABI version, and architecture of the current process and then downloads it, extracting it into the module path. If a corresponding prebuilt package is not found, node-gyp is invoked to build the package for the current platform.

Prebuilt Versions

| OS | Architectures | |---------------|---------------------------| | macOS | x64, arm64 | | Linux (glibc) | ia32, x64, armv6, aarch64 | | Linux (musl) | x64, armv6, aarch64 | | Windows | ia32, x64 |

We only provide prebuilt binaries for Node.js 16 and Electron 16.0.0 or higher. Pls note that prebuilds for Electron 28 are not supplied due to build issues.

Build / Package

Please note releasing this package uses GitHub actions.

This flows takes the branch selected from the workflow start drop down, and creates a GitHub and NPM Release containing the prebuild artifacts. The version of the Release comes from the package.json, and in the case of a BETA release automatically appends the beta release version. During processing, it leverages a branch called release-candidate as a holding area for prebuilds.

When running the job, most times a couple of the instances of the sub step Commit & Push Changes within Prebuild NPM and GitHub Release artifacts fails. When this occurs just re-run. This is due to concurrency issues between the steps and GitHub. A typical run has 3-4 steps fail.

  1. Create branch release-candidate if not existing (the script deletes it before starting and will fail if it isn't present)
  2. Ensure version tag within package.json reflects version you want to publish, please note beta tags are added by the action.
  3. Run Action Run prebuild's and Create GitHub and NPM release, and select branch you wish to publish, and if it needs to be BETA tagged and versioned
  4. This will run for about an hour, and create a GitHub release with the prebuild artifacts attached, and a npm release with the prebuild artifacts attached

License

  • Copyright (c) 2012-2015, Christopher Jeffrey (MIT License).
  • Copyright (c) 2016, Daniel Imms (MIT License).
  • Copyright (c) 2018, Microsoft Corporation (MIT License).
  • Copyright (c) 2018, David Wilson (MIT License).
  • Copyright (c) 2018, oznu (MIT License).
  • Copyright (c) 2023, Homebridge (MIT License).