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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@tiddlywiki/mws

v0.2.2

Published

TiddlyWiki Multiple Wiki Server

Readme

MultiWikiServer


Multiple users, multiple wikis for TiddlyWiki.

  • Bag & Recipe system for storing tiddlers.
  • User and Role management with ACL.
  • Multiple database engines supported, using Prisma.
  • Third-party OAuth and password-based login.

Flexible and Extendible

  • Plugins can add routes and hooks.
  • Abstractions everywhere, allowing flexibility.
  • The source code is fully typed and easy to navigate.
  • Admin endpoints can also be called from the CLI.

Most of these features are still in development.

Here's a sneak peak at the new UI that's coming

Dark Mode

Light Mode

Warning: Security between users is still a dumpster fire.

While the database structure is reliable, the security mechanism is more like swiss cheese.

Do not use it to protect feelings or intellectual property.

There are plenty of ways for anyone with write access to get around the security restrictions.

Also, this is a database, please make backups

Databases try very hard to be perfect, and data bugs are rare. But that doesn't mean things can't go wrong. Backups are pretty important.

How to run

The init command creates a new folder and installs what you need to get started. You can name "my-folder" whatever you want.

  • npm init @tiddlywiki/mws@latest my-folder
  • cd my-folder
  • npx mws listen --listener

You can run npx mws help to get more information about the commands.

  • the server runs on port 8080. It does not use HTTPS by default, but you can enable it by specifying a key and cert.
  • A passwords.key file is created which contains the password master salt. If this file changes, all passwords will become unusable and need to be reset.
  • Your database is in the store folder. All files in the store folder are data files, not temp or lock files! Never delete them!

The initial user created on first run has the username admin and password 1234.

If you run into trouble, or need help figuring something out, feel free to start a discussion. If you know what's wrong, you can also open an issue.

Updates

Within 0.x versions, please do NOT use npm install to update your instance from one minor version to the next.

To update between 0.x versions, open each wiki and click the cloud status icon, then click "save snapshot for offline use". You can then create a new instance and import your wikis via the browser.

Always, always, always save a backup of your store folder before updating.

Starting with 0.2

  • You can update to the latest version of MWS using npm update.
  • You can update to the latest version of tiddywiki using npx mws update-tiddlywiki.

If there are any database changes, MWS should pick them up and apply them on startup. The changes are generated by prisma's builtin migration and are supposed to preserve data, but backups are still highly recommended.

Backups

It is recommended to backup your entire data folder, not just the store folder, with a few exceptions.

  • You must always backup the entire store folder. Never delete any files in the store folder. All files in the store folder are data files!
  • passwords.key can be backed up, but since it never changes you could also just save a copy of it in a more secure location separate from your normal backups.
  • You should backup package.json and package-lock.json.
  • The node_modules folder can be ignored. npm ci will reinstall the node_modules folder based on package-lock.json.
  • The cache folder (next to the store folder) is generated every time MWS starts, so it's nothing but bloat. You can always ignore it.
  • Only the tw5/versions.txt file needs to be saved from the tw5 folder.

So essentially, the paths you need to backup are:

  • /package.json
  • /package-lock.json
  • /store
  • /tw5/versions.txt
  • /passwords.key (or save it separately)

Development

In 0.2, the development data folder is /dev/wiki.

If you want to work on the project, or just try out the latest changes,

  • git clone https://github.com/TiddlyWiki/MultiWikiServer
  • cd MultiWikiServer
  • npm install or npm run install-android
  • npm run certs - if you want https (unix only)
  • npm start update-tiddlywiki - Download the latest TiddlyWiki version
  • npm start init-store - Create the admin user and import default wikis.
  • npm start - this will run the build every time, but it's very fast.

The development wiki will be active at http://localhost:8080/

You can change the listeners as explained in the mws.dev.mjs file.