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

codem

v0.4.1

Published

easily embed VSCode web-standalone in projects

Readme

codem

easily embed VSCode web-standalone in projects

Installation

# npm
$ npm install -D codem

# pnpm
$ pnpm add -D codem

# yarn
$ yarn add -D codem

Quick Start

1. Create Config File

Config file can be one of the following:

  • codem.config.ts
  • codem.config.mts
  • codem.config.js
  • codem.config.mjs
  • codem.config.json
// codem.config.ts
import { defineConfig, VscodeChannel } from 'codem'

export default defineConfig({
  // Use stable or insider channel
  channel: VscodeChannel.Stable,
  
  // Specify VSCode version (optional)
  version: '1.96.1'
  
  // Or use a specific commit hash from microsoft/vscode repository (takes precedence over version)
  // commit: '123abc...',

  // The output directory for downloaded VSCode files
  output: './public/vscode'
})

2. Run CLI

npx codem

3. Use VSCode in your project

// import entry from the codem ${output}/index.js
import workbench from '/vscode/index.js'

await workbench.create(window.document.body, {
  // vscode workbench construction options
  productConfiguration: {
    nameShort: "VSCode",
    nameLong: "VSCode in My Project",
    applicationName: "vscode-in-my-project",
    dataFolderName: ".vscode-in-my-project",
    version: "1.0.0",
  },
  // ... other options
})

See Web Workbench API for more available options.

Examples

License

MIT License