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

v1.201704190613.0

Published

A daily build of microsoft monaco

Downloads

3,615

Readme

Monaco

BuildStatus

A daily automated build of Microsoft Monaco.

Warning: This is personal endeavour.

Why?

If you just want a quick editor on a web page the monaco-editor will get you there quicker : https://www.npmjs.com/package/monaco-editor. This internally uses stuff like monaco-langauges and monaco-editor-core.

But if you want to specialize the experience for a particular language (in our case JavaScript/TypeScript as we do in alm.tools) you can use this as a reference for build automation to make your own version.

Some notes on vscode dirs

  • src : the source code
  • out-* (e.g. out-editor) : the built assets
  • build : scripts for building various stuff (including monaco)

How monaco-editor-core is built

Please see vscode/build/monaco/README.md. We simplified it and the process is documented in prepare.sh. Some notes on monaco-editor-core:

  • the build/gulpfile.editor.js contains the monaco building stuff.
  • the monaco.d.ts api is built with build/monaco/api.ts.

Note: the monaco.d.ts.recipe is loosely related to editor.main.ts etc. You get to use the outcome of the recipe (i.e. monaco.d.ts) as typeof monaco.something in your editor.main stuff to ensure types match but it can fail silently due to excessive use of any so be careful 🌹

Also @internal stuff is stripped by api.ts, if you try to bring it all in you will get errors as a lot of stuff is hidden and you will need to bring in all of it using api + editor.main (quite a bit of work.)

Our Build

All done using prepare.sh (with the help of stuff in the extensions folder).

Submodules

Monaco is in the process of making more addons. Best to add them with

git submodule add https://github.com/Microsoft/monaco-css.git

And then add the path to .npmignore

Finally you need to figure out how to integrate it in editor.main

Installation

Due to limited testing and automated release we recommend hard version installs:

npm install monaco --save --save-exact

You can put this your package.json to make it easier for you to update to latest (and now you can npm run umonaco):

    "umonaco": "npm install nmonaco@latest --save --save-exact && npm run tsc",