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-lyra/create-app

v0.7.53

Published

Scaffold a new Eclipse Lyra app (monorepo with app + example extension)

Downloads

3,044

Readme

@eclipse-lyra/create-app

Scaffold a new Eclipse Lyra app with a single command.

Testing locally

From the Eclipse Lyra monorepo root, run the CLI with Node (no publish needed):

node packages/create-app/index.js my-app
# or non-interactive:
node packages/create-app/index.js my-app --yes

Or use npx with the package path:

npx file:./packages/create-app my-app --yes

Then cd my-app && npm run dev to run the scaffolded app.

Usage (published package)

npm create @eclipse-lyra/app

With a project name (directory):

npm create @eclipse-lyra/app my-app

To skip prompts when a project name is provided:

npm create @eclipse-lyra/app my-app -- --yes

Next steps

After scaffolding:

cd my-app
npm run dev

From the created project root, npm run dev runs the app (Vite). Use npm run build and npm run preview to build and preview.

What you get

  • A monorepo with two workspace packages:
    • packages/app – the Lyra app (Vite, core + extensions from npm).
    • packages/example-extension – a minimal example extension you can copy or extend.
  • The app registers a logo contribution on the left main toolbar (slot start) with the text my!app; you can change it in packages/app/src/main.ts.
  • The example extension is loaded by the app and adds an "Example" view in the left side panel.

Example extension

The template includes an example extension in packages/example-extension to show how to build your own extensions without publishing a separate npm package.

  • src/index.ts – Registers the extension with extensionRegistry.registerExtension() (id, name, description, loader, icon). Same pattern as published extensions like @eclipse-lyra/extension-howto-system and @eclipse-lyra/extension-utils.
  • src/example-extension-loader.ts – Loaded when the extension is activated. Registers a TabContribution to SIDEBAR_MAIN (the left side panel), so the "Example" tab appears alongside the workspace file browser.
  • tsconfig.json – TypeScript config for the extension (IDE and type-checking).
  • vite.config.ts – Vite lib build; run npm run build -w example-extension to output dist/ when you want to publish the extension.

You can edit packages/example-extension in place, add more views or contributions, or copy it to start a new extension. The app depends on it via "example-extension": "*" in packages/app/package.json (npm links the workspace package). The app compiles the extension from source in dev; use the extension’s build script if you publish it as a separate package.