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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@caudex/codex-editor

v1.1.0

Published

Codex editor

Readme

Codex text editor

This repository contains the text editor module used in Codex. The Codex editor is based off of the Toast UI editor, and it is composed of the React wrapper and the tui-editor itself.

Installation

To download the editor, run git submodule update --init --recursive from the root directory of /codex. This will clone the editor submodule into its folder.

Next, build the editor by running cd editor && npm install && npm run build.

To install into the client, run npm install --save ../codex-editor from /codex/client. This installs the editor as a node module so that it can be used by the client.

Development

Making changes to the editor and seeing these changes in real-time requires a few configuration steps:

  1. To link changes to the editor to the one installed in /codex/client, run npm link in /codex/codex-editor and then npm link @caudex/codex-editor. Otherwise, npm install --save ../codex-editor must be run after each change to the editor.
  2. The files for the editor itself are contained inside the editor directory and compiled using webpack into single files for the editor and viewer that the React wrapper then uses. Compiling from scratch takes about 20 seconds, but changes can be automatically compiled in ~1s by building the editor in watch mode. To do this, run npm run watch from the editor directory.