spec-up-t 0.11.1

package/.history/index_20240609131847.js

@@ -0,0 +1,394 @@
+
+module.exports = function(options = {}) {
+
+  const {
+    fetchExternalSpecs,
+    validateReferences,
+    findExternalSpecByKey
+  } = require('./references.js');
+  const {getXrefsData} = require('./src/get-xrefs-data.js');
+  const gulp = require('gulp');
+  const fs = require('fs-extra');
+  const path = require('path');
+  const findPkgDir = require('find-pkg-dir');
+  const modulePath = findPkgDir(__dirname);
+  let config = fs.readJsonSync('./specs.json');
+  let assets = fs.readJsonSync(modulePath + '/src/asset-map.json');
+  let externalReferences;
+  let references = [];
+  let definitions = [];
+
+  const katexRules = ['math_block', 'math_inline']
+  const replacerRegex = /\[\[\s*([^\s\[\]:]+):?\s*([^\]\n]+)?\]\]/img;
+  const replacerArgsRegex = /\s*,+\s*/;
+  const replacers = [
+    {
+      test: 'insert',
+      transform: function(path){
+        if (!path) return '';
+        return fs.readFileSync(path, 'utf8');
+      }
+    }
+  ];
+
+  // getXrefsData();
+
+  // Get the current working directory
+  const projectRoot = process.cwd();
+  // Create a path for the output file in the project root
+  const inputPath = path.join(projectRoot, 'output/xrefs-data.js');
+  // Read './xrefs-data.js' as a string
+  let xrefsData;
+  try {
+    if (fs.existsSync(inputPath)) {
+      xrefsData = fs.readFileSync(inputPath, 'utf8');
+      xrefsData = '<script>' + xrefsData + '</script>';
+    } else {
+      xrefsData = "";
+    }
+  } catch (error) {
+    console.error(error);
+    xrefsData = "";
+  }
+
+
+
+  console.log('xrefsData: ', xrefsData);
+
+
+
+  function applyReplacers(doc) {
+    return doc.replace(replacerRegex, function (match, type, args) {
+      let replacer = replacers.find(r => type.trim().match(r.test));
+      return replacer ? replacer.transform(...args.trim().split(replacerArgsRegex)) : match;
+    });
+  }
+
+  function normalizePath(path){
+    return path.trim().replace(/\/$/g, '') + '/';
+  }
+
+  function renderRefGroup(type){
+    let group = specGroups[type];
+    if (!group) return '';
+    let html = Object.keys(group).sort().reduce((html, name) => {
+      let ref = group[name];
+      return html += `
+        <dt id="ref:${name}">${name}</dt>
+        <dd>
+          <cite><a href="${ref.href}">${ref.title}</a></cite>. 
+          ${ref.authors.join('; ')}; ${ref.rawDate}. <span class="reference-status">Status: ${ref.status}</span>.
+        </dd>
+      `;
+    }, '<dl class="reference-list">')
+    return `\n${html}\n</dl>\n`;
+  }
+
+  function findKatexDist(){
+    const relpath = "node_modules/katex/dist";
+    const paths = [
+      path.join(process.cwd(), relpath),
+      path.join(__dirname, relpath),
+    ];
+    for(const abspath of paths) {
+      if(fs.existsSync(abspath)) {
+        return abspath
+      }
+    }
+    throw Error("katex distribution could not be located");
+  }
+
+  try {
+
+    var toc;
+    var specGroups = {};
+    const noticeTypes = {
+      note: 1,
+      issue: 1,
+      example: 1,
+      warning: 1,
+      todo: 1
+    };
+    const spaceRegex = /\s+/g;
+    const specNameRegex = /^spec$|^spec[-]*\w+$/i;
+    const terminologyRegex = /^def$|^ref$|^xref/i;
+    const specCorpus = fs.readJsonSync(modulePath + '/assets/compiled/refs.json');
+    const containers = require('markdown-it-container');
+    const md = require('markdown-it')({
+        html: true,
+        linkify: true,
+        typographer: true
+      })
+      .use(require('./src/markdown-it-extensions.js'), [
+        {
+          filter: type => type.match(terminologyRegex),
+          parse(token, type, primary){
+            if (!primary) return;
+            if (type === 'def'){
+              definitions.push(token.info.args);
+              return token.info.args.reduce((acc, syn) => {
+                return `<span id="term:${syn.replace(spaceRegex, '-').toLowerCase()}">${acc}</span>`;
+              }, primary);
+            }
+            else if (type === 'xref') {
+              const url = findExternalSpecByKey(config, token.info.args[0]);
+              const term = token.info.args[1].replace(spaceRegex, '-').toLowerCase();
+              return `<a class="term-reference" data-local-href="#term:${token.info.args[0]}:${term}"
+                href="${url}#term:${term}">${token.info.args[1]}</a>`;
+            }
+            else {
+              references.push(primary);
+              return `<a class="term-reference" href="#term:${primary.replace(spaceRegex, '-').toLowerCase()}">${primary}</a>`;
+            }
+          }
+        },
+        {
+          filter: type => type.match(specNameRegex),
+          parse(token, type, name){
+            if (name) {
+              let _name = name.replace(spaceRegex, '-').toUpperCase();
+              let spec = specCorpus[_name] ||
+                         specCorpus[_name.toLowerCase()] || 
+                         specCorpus[name.toLowerCase()] || 
+                         specCorpus[name];
+              if (spec) {
+                spec._name = _name;
+                let group = specGroups[type] = specGroups[type] || {};
+                token.info.spec = group[_name] = spec;
+              }
+            }
+          },
+          render(token, type, name){
+            if (name){
+              let spec = token.info.spec;
+              if (spec) return `[<a class="spec-reference" href="#ref:${spec._name}">${spec._name}</a>]`;
+            }
+            else return renderRefGroup(type);
+          }
+        }
+      ])
+      .use(require('markdown-it-attrs'))
+      .use(require('markdown-it-chart').default)
+      .use(require('markdown-it-deflist'))
+      .use(require('markdown-it-references'))
+      .use(require('markdown-it-icons').default, 'font-awesome')
+      .use(require('markdown-it-ins'))
+      .use(require('markdown-it-mark'))
+      .use(require('markdown-it-textual-uml'))
+      .use(require('markdown-it-sub'))
+      .use(require('markdown-it-sup'))
+      .use(require('markdown-it-task-lists'))
+      .use(require('markdown-it-multimd-table'), {
+        multiline:  true,
+        rowspan:    true,
+        headerless: true
+      })
+      .use(containers, 'notice', {
+        validate: function(params) {
+          let matches = params.match(/(\w+)\s?(.*)?/);
+          return matches && noticeTypes[matches[1]];
+        },
+        render: function (tokens, idx) {
+          let matches = tokens[idx].info.match(/(\w+)\s?(.*)?/);
+          if (matches && tokens[idx].nesting === 1) {
+            let id;
+            let type = matches[1];
+            if (matches[2]) {
+              id = matches[2].trim().replace(/\s+/g , '-').toLowerCase();
+              if (noticeTitles[id]) id += '-' + noticeTitles[id]++;
+              else noticeTitles[id] = 1;
+            }
+            else id = type + '-' + noticeTypes[type]++;
+            return `<div id="${id}" class="notice ${type}"><a class="notice-link" href="#${id}">${type.toUpperCase()}</a>`;
+          }
+          else return '</div>\n';
+        }
+      })
+      .use(require('markdown-it-prism'))
+      .use(require('markdown-it-toc-and-anchor').default, {
+        tocClassName: 'toc',
+        tocFirstLevel: 2,
+        tocLastLevel: 4,
+        tocCallback: (_md, _tokens, html) => toc = html,
+        anchorLinkSymbol: '§',
+        anchorClassName: 'toc-anchor'
+      })
+      .use(require('@traptitech/markdown-it-katex'))
+
+    async function render(spec, assets) {
+      try {
+        noticeTitles = {};
+        specGroups = {};
+        console.log('Rendering: ' + spec.title);
+        return new Promise(async (resolve, reject) => {
+          Promise.all((spec.markdown_paths || ['spec.md']).map(_path => {
+            return fs.readFile(spec.spec_directory + _path, 'utf8').catch(e => reject(e))
+          })).then(async docs => {
+            const features = (({ source, logo }) => ({ source, logo }))(spec);
+            if (spec.external_specs && !externalReferences) {
+              externalReferences = await fetchExternalSpecs(spec);
+            }
+            let doc = docs.join("\n");
+            doc = applyReplacers(doc);
+            md[spec.katex ? "enable" : "disable"](katexRules);
+            const render = md.render(doc);
+            fs.writeFile(path.join(spec.destination, 'index.html'), `
+              <!DOCTYPE html>
+              <html lang="en">
+                <head>
+                  <meta charset="utf-8">
+                  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+                  <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
+      
+                  <title>${spec.title}</title>
+
+                  <link href="https://fonts.googleapis.com/css2?family=Heebo:wght@300;400&display=swap" rel="stylesheet">
+
+                  ${assets.head}
+                  ${xrefsData}
+                </head>
+                <body features="${Object.keys(features).join(' ')}">
+                  
+                  ${assets.svg}
+      
+                  <main>
+      
+                    <header id="header" class="panel-header">
+                      <span id="toc_toggle" panel-toggle="toc">
+                        <svg icon><use xlink:href="#svg-nested-list"></use></svg>
+                      </span>
+                      <a id="logo" href="${spec.logo_link ? spec.logo_link : '#_'}">
+                        <img src="${spec.logo}" />
+                      </a>
+                      <span issue-count animate panel-toggle="repo_issues">
+                        <svg icon><use xlink:href="#svg-github"></use></svg>
+                      </span>
+                    </header>
+      
+                    <article id="content">
+                      ${render}
+                    </article>    
+      
+                  </main>
+      
+                  <slide-panels id="slidepanels">
+                    <slide-panel id="repo_issues" options="right">
+                      <header class="panel-header">
+                        <span>
+                          <svg icon><use xlink:href="#svg-github"></use></svg>
+                          <span issue-count></span>
+                        </span>
+                        <span class="repo-issue-toggle" panel-toggle="repo_issues">✕</span>
+                      </header>
+                      <ul id="repo_issue_list"></ul>
+                    </slide-panel>
+      
+                    <slide-panel id="toc">
+                      <header class="panel-header">
+                        <span>Table of Contents</span>
+                        <span panel-toggle="toc">✕</span>
+                      </header>
+                      <div id="toc_list">
+                        ${toc}
+                      </div>
+                    </slide-panel>
+                    
+                  </slide-panels>
+                  <div style="display: none;">
+                    ${externalReferences}
+                  </div>
+                </body>
+                <script>window.specConfig = ${JSON.stringify(spec)}</script>
+                ${assets.body}
+              </html>
+            `, function(err, data){
+              if (err) {
+                reject(err);
+              }
+              else {
+                resolve();
+              }
+            });
+            validateReferences(references, definitions, render);
+            references = [];
+            definitions = [];
+          });
+        });
+      }
+      catch(e) {
+        console.error(e);
+      }
+    }
+
+    config.specs.forEach(spec => {
+      spec.spec_directory = normalizePath(spec.spec_directory);    
+      spec.destination = normalizePath(spec.output_path || spec.spec_directory);
+
+      fs.ensureDirSync(spec.destination);
+
+      let assetTags = {
+        svg: fs.readFileSync(modulePath + '/assets/icons.svg', 'utf8') || ''
+      };
+
+      let customAssets = (spec.assets || []).reduce((assets, asset) => {
+        let ext = asset.path.split('.').pop();
+        if (ext === 'css') {
+          assets.css += `<link href="${asset.path}" rel="stylesheet"/>`;
+        }
+        if (ext === 'js') {
+          assets.js[asset.inject || 'body'] += `<script src="${asset.path}" ${ asset.module ? 'type="module"' : '' } ></script>`;
+        }
+        return assets;
+      }, {
+        css: '',
+        js: { head: '', body: '' }
+      });  
+
+      if (options.dev) {
+        assetTags.head = assets.head.css.map(_path => `<link href="${_path}" rel="stylesheet"/>`).join('') + 
+                         customAssets.css +
+                         assets.head.js.map(_path =>  `<script src="${_path}"></script>`).join('') +
+                         customAssets.js.head;
+        assetTags.body = assets.body.js.map(_path => `<script src="${_path}" data-manual></script>`).join('') + 
+                         customAssets.js.body;
+      }
+      else {
+        assetTags.head = `
+          <style>${fs.readFileSync(modulePath + '/assets/compiled/head.css', 'utf8')}</style>
+          ${ customAssets.css }
+          <script>${fs.readFileSync(modulePath + '/assets/compiled/head.js', 'utf8')}</script>
+          ${ customAssets.js.head }
+        `;
+        assetTags.body = `<script>${fs.readFileSync(modulePath + '/assets/compiled/body.js', 'utf8')}</script>
+                          ${ customAssets.js.body }`;
+      }
+
+      if (spec.katex) {
+        const katexDist = findKatexDist();
+        assetTags.body += `<script>/* katex */${fs.readFileSync(path.join(katexDist, 'katex.min.js'),
+                          'utf8')}</script>`;
+        assetTags.body += `<style>/* katex */${fs.readFileSync(path.join(katexDist, 'katex.min.css'),
+                          'utf8')}</style>`;
+        
+        fs.copySync(path.join(katexDist, 'fonts'), path.join(spec.destination, 'fonts'));
+      }
+
+      if (!options.nowatch) {
+        gulp.watch(
+          [spec.spec_directory + '**/*', '!' + path.join(spec.destination, 'index.html')],
+          render.bind(null, spec, assetTags)
+        )
+      }
+
+      render(spec, assetTags).then(() => {
+        if (options.nowatch) process.exit(0)
+      }).catch(() => process.exit(1));
+
+    });
+
+  }
+  catch(e) {
+    console.error(e);
+  }
+
+}

package/.history/multi-file-test/abstract_20240529170917.md

@@ -0,0 +1,3 @@
+## Abstract
+
+Let's face it, other tools and generators for writing technical specifications aimed at standards bodies or industry groups are cumbersome, underwhelming, and lack the features you might want in a technical specification document. Spec-Up's goal is to deliver you a better spec-writing experience with far less effort and tedium than other tools in the ecosystem. Spec-Up is a dead simple tool that auto-generates great specs from markdown. The version of markdown Spec-up uses contains all the same features you might expect from common implementations, like GitHub, but adds much more, including notice blocks, complex tables, charts, advanced syntax highlighting, UML diagrams, etc. 

package/.history/multi-file-test/abstract_20240529171417.md

@@ -0,0 +1,3 @@
+## Abstract
+
+kor11 Let's face it, other tools and generators for writing technical specifications aimed at standards bodies or industry groups are cumbersome, underwhelming, and lack the features you might want in a technical specification document. Spec-Up's goal is to deliver you a better spec-writing experience with far less effort and tedium than other tools in the ecosystem. Spec-Up is a dead simple tool that auto-generates great specs from markdown. The version of markdown Spec-up uses contains all the same features you might expect from common implementations, like GitHub, but adds much more, including notice blocks, complex tables, charts, advanced syntax highlighting, UML diagrams, etc.

package/.history/multi-file-test/getting-started_20240529170917.md

@@ -0,0 +1,21 @@
+## Getting Started
+
+Using Spec-Up is easy peasy lemon squeezy:
+
+1. `npm install spec-up`
+2. Create a subdirectory in your project with two files:
+    - `spec.json` - add some basic config values, like your desired HTML page title, etc.
+    - `spec.md` - write the markdown version of your spec here (duh)
+3. In your main node.js file, drop in this bad boy: `require('spec-up')()`
+
+Boom! That's it. Spec-Up will auto-detect the location of your spec files and auto-generate your spec's HTML version every time you hit save after editing your `spec.md` files. Did I mention you can have multiple specs located at any depth in your project and Spec-Up will crawl up in there and render all those specs like a damn boss? Well it does, because why the hell not.
+
+**Usage**
+
+If your `spec.json` and `package.json` and `package-lock.json` files are in working order, Spec-up can be called from the root of your repo in three different modes:
+
+|command|behavior|
+|---|---|
+|`npm run edit`|after rendering, this will stay running and the `gulp` library will watch the source files in your spec directory/ies for changes and re-render any time you save a file. Opening these rendered files in a browser and refreshing them will keep you up to date.|
+|`npm run render`|this renders the site once and does not keep a gulpy watch on the underlying files.|
+|`npm run dev`|this enables debugging features.|

package/.history/multi-file-test/getting-started_20240601200253.md

@@ -0,0 +1,24 @@
+## Getting Started
+
+[[xref: PE2, ACDC]]
+[[xref: PE2, ACD]]
+
+Using Spec-Up is easy peasy lemon squeezy:
+
+1. `npm install spec-up`
+2. Create a subdirectory in your project with two files:
+    - `spec.json` - add some basic config values, like your desired HTML page title, etc.
+    - `spec.md` - write the markdown version of your spec here (duh)
+3. In your main node.js file, drop in this bad boy: `require('spec-up')()`
+
+Boom! That's it. Spec-Up will auto-detect the location of your spec files and auto-generate your spec's HTML version every time you hit save after editing your `spec.md` files. Did I mention you can have multiple specs located at any depth in your project and Spec-Up will crawl up in there and render all those specs like a damn boss? Well it does, because why the hell not.
+
+**Usage**
+
+If your `spec.json` and `package.json` and `package-lock.json` files are in working order, Spec-up can be called from the root of your repo in three different modes:
+
+|command|behavior|
+|---|---|
+|`npm run edit`|after rendering, this will stay running and the `gulp` library will watch the source files in your spec directory/ies for changes and re-render any time you save a file. Opening these rendered files in a browser and refreshing them will keep you up to date.|
+|`npm run render`|this renders the site once and does not keep a gulpy watch on the underlying files.|
+|`npm run dev`|this enables debugging features.|

package/.history/multi-file-test/getting-started_20240601200322.md

@@ -0,0 +1,21 @@
+## Getting Started
+
+Using Spec-Up is easy peasy lemon squeezy:
+
+1. `npm install spec-up`
+2. Create a subdirectory in your project with two files:
+    - `spec.json` - add some basic config values, like your desired HTML page title, etc.
+    - `spec.md` - write the markdown version of your spec here (duh)
+3. In your main node.js file, drop in this bad boy: `require('spec-up')()`
+
+Boom! That's it. Spec-Up will auto-detect the location of your spec files and auto-generate your spec's HTML version every time you hit save after editing your `spec.md` files. Did I mention you can have multiple specs located at any depth in your project and Spec-Up will crawl up in there and render all those specs like a damn boss? Well it does, because why the hell not.
+
+**Usage**
+
+If your `spec.json` and `package.json` and `package-lock.json` files are in working order, Spec-up can be called from the root of your repo in three different modes:
+
+|command|behavior|
+|---|---|
+|`npm run edit`|after rendering, this will stay running and the `gulp` library will watch the source files in your spec directory/ies for changes and re-render any time you save a file. Opening these rendered files in a browser and refreshing them will keep you up to date.|
+|`npm run render`|this renders the site once and does not keep a gulpy watch on the underlying files.|
+|`npm run dev`|this enables debugging features.|

package/.history/multi-file-test/getting-started_20240601200328.md

@@ -0,0 +1,21 @@
+## Getting Started
+
+Using Spec-Up is easy peasy lemon squeezy:
+
+1. `npm install spec-up`
+2. Create a subdirectory in your project with two files:
+    - `spec.json` - add some basic config values, like your desired HTML page title, etc.
+    - `spec.md` - write the markdown version of your spec here (duh)
+3. In your main node.js file, drop in this bad boy: `require('spec-up')()`
+
+Boom! That's it. Spec-Up will auto-detect the location of your spec files and auto-generate your spec's HTML version every time you hit save after editing your `spec.md` files. Did I mention you can have multiple specs located at any depth in your project and Spec-Up will crawl up in there and render all those specs like a damn boss? Well it does, because why the hell not.
+
+**Usage**
+
+If your `spec.json` and `package.json` and `package-lock.json` files are in working order, Spec-up can be called from the root of your repo in three different modes:
+
+|command|behavior|
+|---|---|
+|`npm run edit`|after rendering, this will stay running and the `gulp` library will watch the source files in your spec directory/ies for changes and re-render any time you save a file. Opening these rendered files in a browser and refreshing them will keep you up to date.|
+|`npm run render`|this renders the site once and does not keep a gulpy watch on the underlying files.|
+|`npm run dev`|this enables debugging features.|

package/.history/multi-file-test/getting-started_20240601200635.md

@@ -0,0 +1,24 @@
+## Getting Started
+
+blah [[xref: PE2, ACDC]] blah
+b;ah [[xref: PE2, ACD]] bla
+
+Using Spec-Up is easy peasy lemon squeezy:
+
+1. `npm install spec-up`
+2. Create a subdirectory in your project with two files:
+    - `spec.json` - add some basic config values, like your desired HTML page title, etc.
+    - `spec.md` - write the markdown version of your spec here (duh)
+3. In your main node.js file, drop in this bad boy: `require('spec-up')()`
+
+Boom! That's it. Spec-Up will auto-detect the location of your spec files and auto-generate your spec's HTML version every time you hit save after editing your `spec.md` files. Did I mention you can have multiple specs located at any depth in your project and Spec-Up will crawl up in there and render all those specs like a damn boss? Well it does, because why the hell not.
+
+**Usage**
+
+If your `spec.json` and `package.json` and `package-lock.json` files are in working order, Spec-up can be called from the root of your repo in three different modes:
+
+|command|behavior|
+|---|---|
+|`npm run edit`|after rendering, this will stay running and the `gulp` library will watch the source files in your spec directory/ies for changes and re-render any time you save a file. Opening these rendered files in a browser and refreshing them will keep you up to date.|
+|`npm run render`|this renders the site once and does not keep a gulpy watch on the underlying files.|
+|`npm run dev`|this enables debugging features.|

package/.history/multi-file-test/getting-started_20240601200947.md

@@ -0,0 +1,23 @@
+## Getting Started
+
+blah [[xref: PE2, ACDC]] blah
+
+Using Spec-Up is easy peasy lemon squeezy:
+
+1. `npm install spec-up`
+2. Create a subdirectory in your project with two files:
+    - `spec.json` - add some basic config values, like your desired HTML page title, etc.
+    - `spec.md` - write the markdown version of your spec here (duh)
+3. In your main node.js file, drop in this bad boy: `require('spec-up')()`
+
+Boom! That's it. Spec-Up will auto-detect the location of your spec files and auto-generate your spec's HTML version every time you hit save after editing your `spec.md` files. Did I mention you can have multiple specs located at any depth in your project and Spec-Up will crawl up in there and render all those specs like a damn boss? Well it does, because why the hell not.
+
+**Usage**
+
+If your `spec.json` and `package.json` and `package-lock.json` files are in working order, Spec-up can be called from the root of your repo in three different modes:
+
+|command|behavior|
+|---|---|
+|`npm run edit`|after rendering, this will stay running and the `gulp` library will watch the source files in your spec directory/ies for changes and re-render any time you save a file. Opening these rendered files in a browser and refreshing them will keep you up to date.|
+|`npm run render`|this renders the site once and does not keep a gulpy watch on the underlying files.|
+|`npm run dev`|this enables debugging features.|

package/.history/multi-file-test/getting-started_20240601201356.md

@@ -0,0 +1,24 @@
+## Getting Started
+
+blah [[xref: PE2, ACDC]] blah
+b;ah [[xref: PE2, ACD]] bla
+
+Using Spec-Up is easy peasy lemon squeezy:
+
+1. `npm install spec-up`
+2. Create a subdirectory in your project with two files:
+    - `spec.json` - add some basic config values, like your desired HTML page title, etc.
+    - `spec.md` - write the markdown version of your spec here (duh)
+3. In your main node.js file, drop in this bad boy: `require('spec-up')()`
+
+Boom! That's it. Spec-Up will auto-detect the location of your spec files and auto-generate your spec's HTML version every time you hit save after editing your `spec.md` files. Did I mention you can have multiple specs located at any depth in your project and Spec-Up will crawl up in there and render all those specs like a damn boss? Well it does, because why the hell not.
+
+**Usage**
+
+If your `spec.json` and `package.json` and `package-lock.json` files are in working order, Spec-up can be called from the root of your repo in three different modes:
+
+|command|behavior|
+|---|---|
+|`npm run edit`|after rendering, this will stay running and the `gulp` library will watch the source files in your spec directory/ies for changes and re-render any time you save a file. Opening these rendered files in a browser and refreshing them will keep you up to date.|
+|`npm run render`|this renders the site once and does not keep a gulpy watch on the underlying files.|
+|`npm run dev`|this enables debugging features.|

package/.history/package_20240529170917.json

@@ -0,0 +1,61 @@
+{
+  "name": "spec-up",
+  "version": "0.10.7",
+  "description": "Technical specification drafting tool that generates rich specification documents from markdown.",
+  "main": "./index",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/decentralized-identity/spec-up.git"
+  },
+  "scripts": {
+    "edit": "node -e \"require('./index')()\"",
+    "render": "node -e \"require('./index')({ nowatch: true })\"",
+    "dev": "node -e \"require('./index')({ dev: true })\""
+  },
+  "keywords": [
+    "spec",
+    "specs",
+    "markdown",
+    "editor",
+    "standards"
+  ],
+  "author": "Daniel Buchner",
+  "license": "Apache 2.0",
+  "bugs": {
+    "url": "https://github.com/decentralized-identity/spec-up/issues"
+  },
+  "homepage": "https://github.com/decentralized-identity/spec-up#readme",
+  "dependencies": {
+    "@traptitech/markdown-it-katex": "3.3.0",
+    "axios": "0.21.2",
+    "find-pkg-dir": "2.0.0",
+    "fs-extra": "8.1.0",
+    "gulp": "4.0.2",
+    "gulp-clean-css": "4.3.0",
+    "gulp-concat": "2.6.1",
+    "gulp-terser": "1.2.0",
+    "jsdom": "^24.0.0",
+    "markdown-it": "13.0.1",
+    "markdown-it-anchor": "5.2.5",
+    "markdown-it-attrs": "4.1.4",
+    "markdown-it-chart": "^0.2.0",
+    "markdown-it-container": "^2.0.0",
+    "markdown-it-deflist": "^2.1.0",
+    "markdown-it-icons": "^0.4.1",
+    "markdown-it-ins": "^2.0.0",
+    "markdown-it-mark": "^2.0.0",
+    "markdown-it-modify-token": "1.0.2",
+    "markdown-it-multimd-table": "^4.1.3",
+    "markdown-it-prism": "^2.2.0",
+    "markdown-it-references": "1.0.0-alpha.10",
+    "markdown-it-sub": "^1.0.0",
+    "markdown-it-sup": "^1.0.0",
+    "markdown-it-task-lists": "2.1.1",
+    "markdown-it-textual-uml": "0.1.3",
+    "markdown-it-toc-and-anchor": "4.2.0",
+    "merge-stream": "2.0.0",
+    "pkg-dir": "4.2.0",
+    "prismjs": ">=1.24.0",
+    "yargs": "16.2.0"
+  }
+}