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

@vencord/venmic

v6.1.0

Published

linux audio screenshare for discord (or any electron app) via pipewire

Downloads

6,327

Readme

venmic - screenshare support for pipewire

[!WARNING]
This project is not intended for standalone usage. You need a modified discord client that makes use of this.

📖 Usage

venmic can be used as node-module or as a local rest-server.

The node-module is mainly intended for internal usage by Vesktop. For a usage example, see the following Vesktop source files:

The Rest-Server exposes three simple endpoints

  • (POST) /list

    List all available applications to share.
    You can optionally define a JSON-Body containing all the props the listed nodes should have (i.e. ["node.name"]).

  • (POST) /link

    Depending on wether or not include or exclude are defined the behavior will change:

    • only include
      • Links nodes that match given props
    • only exclude
      • Links nodes that do not match given props
    • both include and exclude
      • Links all applications that match props in include and not those given in exclude

    The setting ignore_devices is optional and will default to true.
    When enabled it will prevent hardware-devices like speakers and microphones from being linked to the virtual microphone.

    The setting only_speakers is optional and will default to true.
    When enabled it will prevent linking against nodes that don't play to a speaker.

    The setting only_default_speakers is optional and will default to true.
    When enabled it will prevent linking against nodes that don't play to the default speaker.

    The setting workaround is also optional and will default to an empty array.
    When set, venmic will redirect the first node that matches all of the specified properties to itself.

  • (GET) /unlink

    Unlinks the currently linked application

🏗️ Compiling

  • Rest-Server

    git clone https://github.com/Vencord/linux-virtmic && cd linux-virtmic
    cmake -B build && cmake --build build
  • Node-Addon

    git clone https://github.com/Vencord/linux-virtmic && cd linux-virtmic
    pnpm install

🐛 Debugging

When reporting an issue please make sure to set the environment variable VENMIC_ENABLE_LOG.

If said variable is set venmic will output a lot of useful information to stdout and a log-file which can be found in ~/.local/state/venmic/venmic.log.

It is highly recommended to include this log file in your issue report otherwise we may not be able to help you!

🤝 Acknowledgements

Kudos to all the developers involved, keep up the great work!