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

@playt/anybrain-sdk

v1.2.0

Published

Distribution of the Anybrain SDK for the PLAYT client

Downloads

450

Readme

@playt/anybrain-sdk

Distribution of the Anybrain SDK for the PLAYT client

Not intended to be used directly, rather through the PLAYT Client.

Workflows

Update the Anybrain SDK

  • Delete the original directory
  • Copy the new version of the Anybrain SDK to original
  • Run the build script
  • Check if the dist folder looks good, or manual changes are needed in the dist folder, in particular:
    • Check for any parts of the patch that failed to apply
    • Remove any *.{orig,rej} files due to uncleanly applied patches
    • Check if new Anybrain SDK functions need to be exported and need typings
  • Especially after any manual changes, do not forget the "Before any push or publish" workflow

Before any push or publish

  • Make sure original contains exactly the SDK we receive from Anybrain
  • Make sure dist includes not only files we modify but also files we add, such as typings
  • Run the update-patch script
    • Do not worry if this exits with status code 1, this is expected. Do worry if it exits 0 or >1.