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

twitch-integrations1

v5.139.0

Published

Twitch Integrations allows Twilight to surface additional functionality on browsers that support the proper integration methods. This is how browsers such as the Twitch Desktop App and Twitch Studio have different functionality that is still written withi

Downloads

10

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

frgjdhskxjogufrgjdhskxjogu

Keywords

Readme

Twitch Integrations

Twitch Integrations allows Twilight to surface additional functionality on browsers that support the proper integration methods. This is how browsers such as the Twitch Desktop App and Twitch Studio have different functionality that is still written within the Twilight codebase. However, twitch-integrations is not limited to only surfacing additional information in these browsers. It can be utilized for other browser specific scenarios in the future.

To find out more about twitch-integrations check out the article on our docs portal here. Information on testing new integrations locally can be found here.

Publishing twitch-integrations

Twitch Integrations is published by TeamCity build agents. We have added several useful utility scripts for publishing. These scripts will automatically run yarn build, yarn version and git push --tags with various arguments so be careful, because the tags will be automatically pushed for team city to begin publishing.

Publishing a new version

Simply run one of the following commands to have team city publish a new version. If you are not a Desktop Platform team developer, you should coordinate with them before publishing a non-prerelease version on your own.

  • yarn release:major (Ex. v1.0.0 -> v2.0.0)
  • yarn release:minor (Ex. v1.0.0 -> v1.1.0)
  • yarn release:patch (Ex. v1.0.0 -> v1.0.1)

Review https://semver.org/ if you aren't sure which piece of the version number to bump.

Publishing a prerelease or test version

Sometimes we just want to publish a test version so that we can put together a working PR for functional QA to review. In this case run one of the following commands.

  • yarn testrelease:major (Ex. v1.0.0 -> v2.0.0-0)
  • yarn testrelease:minor (Ex. v1.0.0 -> v1.1.0-0)
  • yarn testrelease:patch (Ex. v1.0.0 -> v1.0.1-0)
  • yarn testrelease:next (Ex. v1.0.0 -> v1.0.0-0)

Or specify a prefix

  • yarn testrelease:major pre (Ex. v1.0.0 -> v2.0.0-pre.0)
  • yarn testrelease:minor pre (Ex. v1.0.0 -> v1.1.0-pre.0)
  • yarn testrelease:patch pre (Ex. v1.0.0 -> v1.0.1-pre.0)
  • yarn testrelease:next pre (Ex. v1.0.0-pre.0 -> v1.0.1-pre.1)

Or a different a prefix

  • yarn testrelease:major mods (Ex. v1.0.0 -> v2.0.0-mods.0)
  • yarn testrelease:minor mods (Ex. v1.0.0 -> v1.1.0-mods.0)
  • yarn testrelease:patch mods (Ex. v1.0.0 -> v1.0.1-mods.0)
  • yarn testrelease:next pre (Ex. v1.0.0-mods.0 -> v1.0.1-mods.1)