@tiddlywiki/mws 0.1.9 → 0.1.11

package/scripts.mjs

@@ -23,7 +23,7 @@ const workspaces = [
         SKIPDTS: "1"
       });
       await start("node --trace-uncaught --trace-warnings mws.dev.mjs", process.argv.slice(3), {
-        // ENABLE_DEV_SERVER: "mws",
+        ENABLE_DEV_SERVER: "mws",
         ENABLE_EXTERNAL_PLUGINS: "1",
       });
       break;
@@ -69,7 +69,7 @@ const workspaces = [
 
 
       await Promise.resolve().then(async () => {
-        await start("mv node_modules node_modules_old");
+        await start("mv node_modules node_modules_off");
       }).then(async () => {
         await start("git clean -dfx tests");
         const filesFolder = path.resolve("create-package/files");
@@ -93,7 +93,7 @@ const workspaces = [
       }).then(async () => {
         await start("npx mws init-store", [], {}, { cwd: "tests" });
       }).finally(async () => {
-        await start("mv node_modules_old node_modules");
+        await start("mv node_modules_off node_modules");
       });
       break;
     }
@@ -118,7 +118,6 @@ function start(cmd, args = [], env2 = {}, { cwd = process.cwd(), pipeOut } = {})
   events.on("exit", (code) => { cp.kill(code); });
 
   if(pipeOut) {
-
     return new Promise((r, c) => {
       const chunks = [];
       cp.stdout.on("data", (data) => {
@@ -138,6 +137,6 @@ function start(cmd, args = [], env2 = {}, { cwd = process.cwd(), pipeOut } = {})
       cp.on("exit", (code) => { if(code) c(code); else r(); });
     });
   }
+}
 
 
-}

package/editions/mws-docs/tiddlers/Bags and Recipes.tid

@@ -1,41 +0,0 @@
-created: 20240309135835396
-modified: 20240309142156125
-title: Bags and Recipes
-type: text/vnd.tiddlywiki
-
-The bags and recipes model is a reference architecture for how tiddlers can be shared between multiple wikis. It was first introduced by TiddlyWeb in 2008.
-
-The principles of bags and recipes can be simply stated:
-
-# Tiddlers are stored in named "bags"
-# Bags have access controls that determines which users can read or write to them
-# Recipes are named lists of bags, ordered from lowest priority to highest
-# The tiddlers within a recipe are accumulated in turn from each bag in the recipe in order of increasing priority. Thus, if there are multiple tiddlers with the same title in different bags then the one from the highest priority bag will be used as the recipe tiddler
-# Wikis are composed by splicing the tiddlers from the corresponding recipe into the standard TW5 HTML template
-
-A very simple example of the recipe/bag model might be for a single user who maintains the following bags:
-
-* ''recipes'' - tiddlers related to cooking recipes
-* ''work'' - tiddlers related to work
-* ''app'' - common tiddlers for customising TiddlyWiki
-
-Those bags would be used with the following recipes:
-
-* ''recipes'' --> recipes, app - wiki for working with recipes, with common custom components
-* ''work'' --> work, app - wiki for working with work, with common custom components
-* ''app'' --> app - wiki for maintaining custom components
-
-All of this will work dynamically, so changes to the app bag will instantly ripple into the affected hosted wikis.
-
-A more complex example might be for a teacher working with a group of students:
-
-* ''student-{name}'' bag for each students work
-* ''teacher-course'' bag for the coursework, editable by the teacher
-* ''teacher-tools'' bag for custom tools used by the teacher
-
-Those bags would be exposed through the following hosted wikis:
-
-* ''student-{name}'' hosted wiki for each students work, including the coursework material
-* ''teacher-course'' hosted wiki for the coursework, editable by the teacher
-* ''teacher'' hosted wiki for the teacher, bringing together all the bags, giving them an overview of all the students work
-

package/editions/mws-docs/tiddlers/Installation.tid

@@ -1,32 +0,0 @@
-created: 20241105133737778
-modified: 20250612235731394
-tags: TableOfContents
-title: Installation
-type: text/vnd.tiddlywiki
-
-These instructions require minimal knowledge of the terminal and require NodeJS to be installed.
-
-# Open a terminal window and set the current directory to the folder you want to create the project folder in. 
-# The init command creates the project folder and installs the required dependencies and config files. You can change the name to whatever you like. <<.copy-code-to-clipboard """npm init @tiddlywiki/mws@latest "new_folder_name" """>>
-# Set the current directory to the project folder that was just created: <<.copy-code-to-clipboard """cd "new_folder_name" """>>
-# Start MWS: <<.copy-code-to-clipboard "npm start">>
-# Visit http://localhost:8080 in a browser on the same computer. 
-# When you have finished using MWS, stop the server with <kbd>ctrl-C</kbd>
-
-See [[Troubleshooting]] if you encounter any errors.
-
-!!! Updating MWS
-
-To update your copy of MWS in the future with newer changes will require re-downloading the code, taking care not to lose any changes you might have made.
-
-# Make a backup: Copy or zip your project folder to a safe backup folder.  <<.copy-code-to-clipboard "tar -cf archive.tar my_folder">>
-# Get the latest version. Notice that the second word is `install` instead of `init`. This pulls the latest version from NPM and installs it. <<.copy-code-to-clipboard "npm install @tiddlywiki/mws@latest --save-exact">>
-# Start the server. On startup, MWS checks the database schema and updates it automatically if there are changes. Normally this works just fine, but it can fail, which is why it's important to save a backup first. <<.copy-code-to-clipboard "npm start">>
-
-!!! Git repo
-
-It is recommended to save a history of your project configuration using git, 
-
-* On Windows you can use [[GitHub Desktop|https://github.com/apps/desktop]]. 
-* On Linux, git is usually preinstalled or available via the default package manager for your distro. 
-