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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@eclipse-glsp/playwright-vscode

v2.9.0-next.2

Published

VS Code integration for the GLSP Playwright testing framework

Readme

@eclipse-glsp/playwright-vscode

VS Code integration for the GLSP Playwright testing framework.

Use this package to test a GLSP diagram editor running inside VS Code. It contributes the VSCode integration, the workbench page objects and the setup fixtures that download VS Code and install the extension under test; everything else comes from @eclipse-glsp/playwright, which is developed in the glsp-core repository.

Usage

Create the integration options with defineVSCodeIntegration() in your Playwright configuration. The returned options carry the factory that the integration fixture uses, so no further registration is needed:

import { defineVSCodeIntegration } from '@eclipse-glsp/playwright-vscode';

const integrationOptions = defineVSCodeIntegration({
    workspace: '../workspace',
    file: 'example1.wf',
    vsixId: 'eclipse-glsp.workflow-vscode-example',
    vsixPath: '/path/to/workflow-vscode-example.vsix',
    storagePath: 'playwright/.storage/vscode.setup.json'
});

Tests need two projects: a setup project that downloads VS Code and installs the VSIX, and the test project that depends on it. See docs/vscode-integration.md.

Tests themselves stay integration-agnostic and keep importing test and expect from @eclipse-glsp/playwright.

Documentation

The framework concepts (integrations, page objects, extensions, flows) are documented once, in the core package: concepts. Only what is specific to VS Code is documented here, under docs/.

Building

This package is built as part of the glsp-vscode-integration workspace:

pnpm install
pnpm compile

License

This program and the accompanying materials are made available under the terms of the Eclipse Public License v. 2.0 which is available at https://www.eclipse.org/legal/epl-2.0, or the GNU General Public License, version 2 with the GNU Classpath Exception.

SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0