This page is part of a static HTML representation of the TiddlyWiki at

Scripts for building


These scripts are used to build and release the content for They are not designed for general purpose use – they resolve problems that are specific to the task of building pushing to GitHub Pages, handling the prerelease builds and bumping version numbers.

Nonetheless, you may find techniques that are useful for your own scripts.

Hosting is served by GitHub Pages from the repository

The scripts live in the repository

Directory structure

These scripts require the following directories to be siblings:

The scripts are designed to be executed with the current directory being the TiddlyWiki5 directory.



The package.json in the root of the repository contains a dependency declaration that specifies the latest official released version of TiddlyWiki to be used when building the release targets:

  "dependencies": {
    "tiddlywiki": "5.1.2"

Environment variables

Some of the scripts use the following environment variables:

  • TW5_BUILD_MAIN_EDITION - the path to the wiki folder to be used as the main edition, generating index.html and encrypted.html
  • TW5_BUILD_OUTPUT - the path to the output folder (defaults to ../
  • TW5_BUILD_TIDDLYWIKI - the pathname of the tiddlywiki.js to be used (defaults to ../


Builds the target files. By default, it uses the version of tiddlywiki specified in the package.json file. This can be overridden with the TW5_BUILD_TIDDLYWIKI environment variable. The following command would select the latest prerelease version of tiddlywiki from the TiddlyWiki5 directory:


Builds the readme files for the TiddlyWiki5 and repos using the released version of TiddlyWiki specified in package.json.

Builds the target files using the latest TiddlyWiki prerelease code and special prerelease edition for the content.

Pushes the latest changes to the directory to GitHub.

Builds the dev prerelease edition.

Builds the prerelease prerelease edition.

Builds the tw5tiddlyweb edition and uploads it to TiddlySpace.

Bumps the version number of the package.json in the TiddlyWiki5 repo and applies the correct version tag to the repo.

Publishes the TiddlyWiki5 repo to npm.


Releasing a new version of TiddlyWiki

Preparation on master

  1. Ensure the new release banner image is up to date
  2. Update master with changes from tiddlywiki-com
  3. Verify the version numbers in $:/config/OfficialPluginLibrary in core/wiki/config/OfficialPluginLibrary.tid
  4. Move the latest release note from the prerelease edition into the edition
  5. Adjust the release date and the released field of the latest release tiddler (eg, Release 5.1.3)
  6. Also adjust the comparison link to point to the tag for the new release
  7. Ensure TiddlyWiki Releases has the new version as the default tab
  8. Adjust the modified time of HelloThere
  9. Make sure master is fully committed

Update Readmes

  1. Edit package.json to the new version number
  2. Run ./bin/ to build the readme files
  3. Commit the new readme files to master
  4. Restore package.json to the previous version number

Make New Release

  1. Run ./bin/verbump "5.1.3" (substituting the correct version number) to update the version number, assign it a tag
  2. Run ./bin/ to publish the release to npm
  3. Verify that the new release of TiddlyWiki is available at

Update release

  1. Update tiddlywiki-com from master and push to GitHub

Cleaning Up

  1. Tweet the release with the text "TiddlyWiki v5.x.x released to #newtiddlywikirelease"

Preparation for the next release in master

  1. Adjust version number in package.json
  2. Adjust version number in bin/
  3. Adjust version number in $:/config/OfficialPluginLibrary (both in editions/ and editions/prerelease/tiddlers/system) and $:/config/LocalPluginLibrary
  4. Adjust new release banner
  5. Create the release note for the new release
  6. Commit changes to master and push to GitHub

Releasing new content for TiddlyWiki

To update with new content, make a Pull Request with the updated tiddlers to the tiddlywiki-com branch. As soon as the PR is merged, the Continuous Deployment system will automatically rebuild the site.

Note that the PR should only include updates within the editions folder of the repo.