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

monaco-editor-workers

v0.45.0

Published

Monaco Editor Worker Support Package

Downloads

36,219

Readme

Monaco Editor Worker Support Package

This package supplies all monaco-editor workers as module or classic workers (bundled with vite/rollup) and it contains a utility function that applies them to MonacoEnvironment:

Workers are now exported in the packages.json. This could be handy for re-bundling.

Additional exports:

  • ./workers/module/editor (Editor Module Worker)
  • ./workers/module/ts (TypeScript/JavaScript Module Worker)
  • ./workers/module/html (HTML Module Worker)
  • ./workers/module/css (CSS Module Worker)
  • ./workers/module/json (JSON Module Worker)
  • ./workers/classic/editor (Editor Classic/Firefox compatible Worker)
  • ./workers/classic/ts (TypeScript/JavaScript Classic/Firefox compatible Worker)
  • ./workers/classic/html (HTML Classic/Firefox compatible Worker)
  • ./workers/classic/css (CSS Classic/Firefox compatible Worker)
  • ./workers/classic/json (JSON Classic/Firefox compatible Worker)
import { buildWorkerDefinition } from "monaco-editor-workers";

// supply path to workers path, the basePath and tell if module (true) or classic (false) workers shall be used.
// Classic workers are still required by Firefox.
buildWorkerDefinition('./node_modules/monaco-editor-workers/dist/workers', import.meta.url, false);

The version of this package is aligned with the version of monaco-editor.

Getting Started

We recommend using Volta to ensure your node & npm are on known good versions.

If you have node.js LTS available, then from the root of the project run:

npm i
npm run build

If you get an error with npm i regarding tree-mending, you can run npm ci to clean things up from previous installations and continue.

Afterwards, launch the Vite development server:

npm run dev

You can find one example (manual human testing) here index.html. They can be used once Vite is running. You can reach it once started on http://localhost:5173.