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 🙏

© 2025 – Pkg Stats / Ryan Hefner

vsc-live-share-pocketbase

v1.4.2

Published

Access other local VSC Live Share sessions by using PocketBase

Readme

VSC Local Sessions (Pocketbase)

Allows you to access VS Code Live Sessions from your other devices by storing session data in a Pocketbase DB.

Preconfiguration

  1. Setup a pocketbase instance (or use an existing one)
  2. Create a new collection called vscode_live_share_sessions
  3. The collection should have the following fields:
    • machineId (string)
    • sessionUrl (string)
    • projectName (string)
    • deviceName (string)
  4. Open VSCode settings and set the 'Pocketbase URL' (vscls.pocketbaseUrl) to your Pocketbase instance URL
  5. If your collection is set to 'admin only', you should set the 'Pocketbase Auth Email' (vscls.pocketbaseEmail) and 'Pocketbase Auth Password' (vscls.pocketbasePassword) settings to your Pocketbase email and password
  6. You can also set your device name in the 'This device name' (vscls.thisDeviceName) setting. If you don't set this, you will be prompted to provide a name each time you create a session

How to use it

IMPORTANT: Creating a new share session will end any current share sessions that are active within this instance of VSCode.

Open editor, start your live session by pressing Ctrl+Shift+p and selecting VSCLS: Create session. You will be prompted to provide a name for the device and a name for the project. This will first create a session with the VSCode Live Share service, then store the session data in your Pocketbase DB.

Once the session is started, you can access it from any other device by pressing Ctrl+Shift+p and selecting VSCLS: Join session. You will be prompted to select a session from the list of available sessions. You will only be able to see sessions that are not for your existing device.

Commands

  • VSCLS: Create session - Creates a new VSCode Live Share session and stores the session data in your Pocketbase DB
  • VSCLS: List sessions - Retrieves all sessions from your Pocketbase DB
  • VSCLS: Delete session - Lists all available sessions - selecting one will delete it from your Pocketbase DB (note: it doesn't end the live share session currently)

Development

Make changes to the src/extension.ts file and run yarn tsc -p ./ && yarn vscode:prepublish (or yarn build) to compile the changes. If you have installed the extension from the same folder as the source code, you should then Ctrl+Shift+p and select Developer: Reload Window to reload the extension.