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

@code-dot-org/maze

v2.16.0

Published

standalone project for the Maze app type

Downloads

2,324

Readme

maze

npm version Travis Build Status codecov

Standalone repo for the Maze app type

Setup Your Project

Check this project out from source:

git clone [email protected]:code-dot-org/maze.git
cd maze

Next, inside the project, you need to install the project's various dependencies.

yarn install

Now you should be able to run all the tests:

yarn test

And spin up a development build of your new project:

yarn build

Integrate with local Code Studio

In this repo:

yarn link

In main repo's apps/ directory:

yarn link @code-dot-org/maze

This will set up a symlink in main repo's apps/node_modules/ to point at your local changes.

Run

yarn run build

in this repo, and then the main repo's apps build should pick the changes up next time it builds.

If you are running yarn start for continuous builds in the main repo, it will pick up the changes once the build in this repo has completed.

Publishing a new version

In /maze: npm login with an authorized npm account. If necessary, create one under your own email, login with our shared dev account and add your new account to the org. After logging in, you may need to authorize your machine (follow the prompt given):

npm login
npm adduser (if necessary)

Still in /maze: checkout main, and ensure it is up-to-date:

git checkout main
git pull

Verify the existing code doesn't have errors or failing tests:

yarn build
yarn test

Then, update the version (which also publishes to npm):

npm version [major|minor|patch|premajor|preminor|prepatch].

Verify there is a new commit on /maze/main with the updated version number.

In the @code-dot-org repo, incorporate the new version of maze:

git checkout -b [maze-updates-we-are-incorporating]
cd apps
yarn add @code-dot-org/[email protected] (ex: yarn add @code-dot-org/[email protected])

Verify yarn.lock and package.json have been updated.

Commit and push changes, and open and merge a PR.