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

@cs125/helpable

v2021.12.1

Published

CS 124 help system based on Jitsi

Downloads

26

Readme

@cs125/mace

npm Docker Image Version (latest by date) License: MIT

React TypeScript support for synchronizing Ace browser editors.

Install

npm i @cs125/mace # client
docker pull cs125/mace # server

Use

For a complete example of how to use @cs125/mace please see the example in the repository.

First, wrap your app in the <MaceProvider /> component, configured to point at your server (if you are using one):

const App: React.FC = () => {
  return (
    <MaceProvider server={yourMaceServer} googleToken={yourGoogleToken}>
      <RestOfYourApp />
    </MaceProvider>
  )
}

Inside the <MaceProvider /> you can use the <MaceEditor /> component as a drop-in replacement for the <AceEditor /> component provided by react-ace. The only difference is that you need to provide an id prop uniquely identifying each editor instance. Generating those IDs is up to you. One way is to generate unique IDs such as UUIDs and save them with the page contents. Another approach is to generate a unique ID that is a combination of the initial editor contents and its position on the page.

Demo

Visit the demo here.