@slugbugblue/trax-cli 0.11.0

package/.dockerignore

@@ -0,0 +1,7 @@
+.dockerignore
+.git*
+.husky
+.npmignore
+Dockerfile
+jsconfig.json
+node_modules

package/.rgignore

@@ -0,0 +1,2 @@
+node_modules
+package-lock.json

package/CHANGELOG.md

@@ -0,0 +1,80 @@
+# @slugbugblue/trax
+
+## 0.11.0 - 2023-03-25
+
+- Pull CLI from `@slugbugblue/trax` into its own repository
+
+## 0.10.0 - 2023-02-11
+
+- Provide timing feedback on the puzzlebot's actions
+- Add license information for puzzle sources
+- Drop support for node 14; node v16.15 is our minimum supported version
+- More puzzles from Martin M. S. Pedersen -- bringing the total to 100+
+- Enhance the docker configuration and document it in the README
+
+## 0.9.0 - 2023-02-05
+
+- CLI improvements:
+
+  - Puzzle information is now stored as notes, to make it searchable
+
+- More puzzles:
+
+  - Martin M. S. Pedersen contributed eleven new puzzles
+
+## 0.8.0 - 2022-12-29
+
+- The `import` CLI command now loads comments from a .trx file
+
+## 0.7.0 - 2022-12-27
+
+- Added a `notes` command to the CLI to add comments to a game
+
+  - all comments are included in the output generated by the `export` command
+  - the latest comment can be used as a text filter by the `list` command
+  - the latest comment is displayed by the `view` and `list` commands
+
+## 0.6.0 - 2022-12-14
+
+- Added shared `puzzles` commands to the CLI:
+
+  - `trax ls puzzles`: see all the puzzles
+  - `trax new puzzle`: start a new puzzle
+
+## 0.5.0 - 2022-12-05
+
+- Added `puzzles` to the CLI:
+
+  - `trax puzzles ls`: see all the puzzles
+  - `trax puzzle new`: start a new puzzle
+
+## 0.4.0 - 2022-11-25
+
+- Utilize the newly added move suggestions from `trax-analyst` to the CLI
+
+  - added the `suggest` CLI command for quick access to a random suggestion
+
+- Use font glyphs for text bubbles in `tty.js` only if one of the following
+  environment variables are defined and non-empty:
+
+  - `NERDFONT`, `POWERLINE`, `P9K_TTY`, `P9K_SSH`
+
+## 0.3.0 - 2022-09-22
+
+- Added the initial work on `trax-analyst`
+
+  - added the `analyze` CLI command to see an analysis
+
+## 0.2.0 - 2022-04-24
+
+- Added tab-completion and completion preview code to the interactive CLI
+- Restructured the CLI by moving most commands to their own file
+- Changed the `view` CLI command to optionally examine previous moves
+
+## 0.1.0 - 2022-04-08
+
+- Added a command-line interface (CLI) `cli.js` which npm will install using the
+  alias `trax`
+- The CLI usage is self-documenting; run `trax help` to get started
+- Initial commands available: `delete`, `export`, `help`, `import`, `list`,
+  `new`, `play`, `select`, `try`, `undo`, `view`

package/CONTRIBUTING.md

@@ -0,0 +1,102 @@
+# Contributing to slugbugblue/trax-cli
+
+Hi, thanks for considering contributing to this project.
+
+If this is your first time working on an open source project, it is recommended
+that you start by reading [How to Contribute to Open Source][howto].
+
+## Ways to contribute
+
+### Improve documentation
+
+One of the simplest ways to get started contributing is to find areas of the
+documentation that are unclear, incorrect, or that have typos or other errors,
+and providing feedback and corrections. You don't have to know how to code or
+even how to use git.
+
+### Identify bugs
+
+If you are aware of something not working as you think it should, feel free to
+open a new issue to let us know. Browsing through the existing open issues and
+adding comments or making clarifications can also be a great way to get started.
+
+### Fixing bugs
+
+If you feel you have a solution to an existing bug, you are welcome to code up
+your solution and submit a merge request. It may take some time to get fully up
+to speed with our coding styles and with the structure of the code, so don't
+feel bad if your merge request receives comments rather than being immediately
+accepted. Simply make any necessary changes, and update the merge request, or
+let us know in a subsequent comment if you think we are misunderstanding the
+merge request.
+
+## Submitting an issue
+
+If you choose to submit an issue, please take the time to ensure that you
+provide as much detail as possible about the issue. A poorly worded or poorly
+researched issue report will unnecessarily delay the issue resolution.
+
+Even if you don't have the time or expertise to fully diagnose the problem, a
+good issue report can be very helpful to us as we seek to improve the code.
+
+## Submitting a merge request
+
+Good merge requests are a fantastic way to contribute to this project. Your
+merge request is going to be accepted more quickly if it is easy to understand.
+Ideally it should be focused on a single item and avoid unrelated commits.
+
+Please ask first before embarking on a major change, such as adding a new
+feature or refactoring the code, otherwise you risk spending a significant
+amount of time working on something that will not be merged into the project.
+
+If you have never submitted a merge request before, no fear. Here is a [quick
+tutorial][howto-mr] on how to create one.
+
+### Merge request steps
+
+- Fork the project and clone it to your own workspace.
+- Get the latest changes and update the project dependencies:
+
+```bash
+$ git checkout develop
+$ git pull upstream develop
+$ rm -rf node_modules
+$ npm install
+```
+
+- Create a new branch to contain your changes:
+
+```bash
+$ git checkout -b <new-branch-name>
+```
+
+- Make your changes.
+- Test your changes.
+
+```bash
+$ npm test
+```
+
+- Push your changes back to your fork.
+
+```bash
+$ git push -u origin <new-branch-name>
+```
+
+- Open a merge request in the [slugbugblue/trax-cli][repo] repo.
+
+## Working with the code
+
+This repository uses [XO][xo] for linting and [Prettier][prettier] for
+formatting. Running `npm test` will produce an error if your changes do not
+conform. You should consider installing the [XO plugin][xo-plugin] for your
+editor to have the linting errors highlighted for you and automatically fixed on
+save. You can also run `npx xo --fix` from the command line to fix most linting
+errors.
+
+[howto]: https://opensource.guide/how-to-contribute/
+[howto-mr]: https://opensource.guide/how-to-contribute/#opening-a-pull-request
+[prettier]: https://prettier.io
+[repo]: https://gitlab.com/slugbugblue/trax-cli
+[xo]: https://github.com/sidresorhus/xo
+[xo-plugin]: https://github.com/sidresorhus/xo#editor-plugins

package/Dockerfile

@@ -0,0 +1,14 @@
+# Use the latest nodejs long-term-support release,
+# on the latest Alpine Linux for its small footprint
+FROM node:lts-alpine
+# Install current source code
+WORKDIR /trax
+COPY . .
+RUN npm install
+# Ensure the data files can be persisted
+WORKDIR /mnt/data
+ENV XDG_CONFIG_HOME=/mnt/data
+ENV XDG_DATA_HOME=/mnt/data
+VOLUME /mnt/data
+# Use the trax CLI as the starting point
+ENTRYPOINT ["/trax/src/cli.js"]

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright © 2021-2023 Chad Transtrum
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,193 @@
+# Trax Command Line interface
+
+This project provides a command-line for working with Trax games and puzzles.
+
+## Description
+
+Trax is a two-player boardless board game invented by David Smith. For more
+information about Trax, including its [rules][traxrules] and
+[history][traxhistory], see the official website at [traxgame.com][traxgame].
+
+The goal of this javascript project is to allow Trax to be played from the
+command line.
+
+## Installation
+
+Installation can be done in one of two ways, each for a slightly different
+purpose.
+
+If you have nodejs installed on your system, you can use the trax CLI by
+installing it globally via `npm`:
+
+```bash
+npm install -g @slugbugblue/trax-cli
+```
+
+If you don't have node installed and want to use the CLI as a docker container:
+
+```bash
+git clone https://gitlab.com/slugbugblue/trax-cli.git ~/trax
+docker build -t trax ~/trax
+```
+
+## CLI Usage
+
+The command-line interface is provided as `trax`, available in your path if
+installed globally, or in the `node_modules/.bin` directory and runnable using
+`npx trax` if installed locally.
+
+> If you installed by creating a Docker image, use the following command to
+> launch the CLI:
+>
+> - `docker run --name trax -itv $HOME/trax:/mnt/data --rm trax`
+>
+> Since that's a bit much to type, it's recommended to create an alias in one of
+> your startup scripts:
+>
+> - `alias trax="docker run --name trax -itv $HOME/trax:/mnt/data --rm trax"`
+>
+> Then you can launch the docker container simply by typing in `trax`, the same
+> as if it were installed globally.
+
+The CLI can be used interactively by running the command with no parameters or
+by passing the `--interactive` or `-i` flag. When run interactively, you can
+avoid worries about the need to escape certain characters from the shell, and it
+can be easier to run multiple commands back to back.
+
+Help is available for the CLI through the use of the `help` command. Type
+`trax help` (or `npx trax help` with a local installation, or simply `help` if
+run interactively) to see a list of the available commands, and `trax help play`
+to see information about the `play` command. Aliases and abbreviations are
+provided to minimize typing and to try to avoid the requirement of memorizing
+the commands. For example, the `list` command has an alias of `ls`, `help` can
+be shortened to `?`, and the `select` command can be activated using `#`.
+
+When you first launch the CLI, you can create a new game using the `new`
+command, and then enter moves for that game using `play`. Since `play` is likely
+to be the most common command used, you can simply omit the command name. For
+example, at the interactive prompt, entering `@0/` is the same as if you had
+entered `play 1. @0/`.
+
+Multiple games can be started at once, and the CLI will remember the currently
+active game and apply future actions to that game. Each game will retain its
+`#id` number until it is deleted, and you can use that number to switch between
+games. For example, to make game \#1 active, enter `select 1` or `select #1` or
+simply `#1` at the interactive prompt.
+
+For ease of working at the command line, the symbols used as the last character
+of the Trax notation can optionally be replaced with letters. Use `s` for slash
+symbol (`/`), `b` for backslash (`\`), and `p` for plus (`+`). While there is no
+need to escape at the interactive prompt, these substitutions will be avilable
+there as well.
+
+### Examples
+
+```text
+# Start a new Trax game with Chad playing as white
+> trax new Chad vs
+
+# Start a new Loop Trax game with Chad playing as black
+> trax new loop vs Chad
+
+# Start a new 8x8 Trax game with Chad as white and Another Player as black
+> trax new 8x8 Chad vs Another Player
+
+# Switch back to the first game. Note the quoting required at the command line.
+# This would not be necessary when running at the interactive prompt.
+> trax '#1'
+
+# Play two moves, using full notation
+> trax play 1. @0/ 2. A0/
+
+# Two more moves, using short notation and symbol substitution
+# B2/ => b2s and A0\ => a0b
+> trax b2s a0b
+
+# See the status of all games
+> trax ls
+```
+
+### Environment variables
+
+The CLI uses standard Windows and Linux [XDG][xdg] file locations as provided by
+the [env-paths library][env-path], with current uses being user-specific
+`config` (`XDG_CONFIG_HOME`) and `data` (`XDG_DATA_HOME`) folders.
+
+In addition, the CLI recognizes several environment variables to determine the
+glyphs to use in the user interface. Setting either `NERDFONT` or `NERDFONTS` to
+any non-empty string will use characters from [Nerdfonts][nerdfont]. Otherwise,
+any of `POWERLINE`, `P9K_TTY`, or `P9K_SSH` will use characters from [Powerline
+fonts][powerline].
+
+## Support
+
+This project is built by [Chad Transtrum][ctrans] as part of the work on
+[slugbugblue.com][sbb]. Issues can be opened on the [gitlab project page][repo].
+
+## Contributing
+
+[Contributions are welcome][contributing]. Ideally in the form of pull requests,
+but feel free to open an issue with a bug report or a suggestion as well.
+
+## Acknowledgments
+
+Many thanks to the late David Smith for coming up with the idea of Trax and for
+his generosity in allowing me to add the game to [GoldToken.com][goldtoken].
+
+Thanks to his widow Colleen Foley-Smith for extending that courtesy to allow me
+to include Trax on [slugbugblue.com][sbb] as well.
+
+I would also like to express my huge heartfelt appreciation to the magnanimous
+[Donald G. Bailey][dgb], who, through his excellent book [Trax Strategy for
+Beginners][traxbook], taught me the basics (and more!) of Trax. I found him
+always ready to share his insights on the mechanics of the game, as well as
+various approaches to encoding its complexities. His undeserved kindness and
+infinite patience in indulging my many questions can never be repaid.
+
+Thanks to [Martin M. S. Pedersen][traxplayer] for contributing ideas, code, and
+puzzles. He's been [curating Trax puzzles][puzzlebook] and [coding solutions for
+Trax][gnutrax] for over two decades, and has a lot of expertise in this area.
+
+## License
+
+Copyright 2019-2023 Chad Transtrum
+
+Licensed under the Apache License, Version 2.0 (the "License"); you may not use
+the files in this project except in compliance with the License. You may obtain
+a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software distributed
+under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
+CONDITIONS OF ANY KIND, either express or implied. See the License for the
+specific language governing permissions and limitations under the License.
+
+## Trax rules copyright
+
+In the United States, game mechanics are not eligible for copyright protection;
+however, the specific wording of game rules does fall under copyright law.
+
+The official rules for Trax are found at http://traxgame.com/about_rules.php.
+
+As Trax is a proprietary game, these rules are the intellectual property of
+David Smith and heirs, and are not to be used without permission.
+
+[contributing]: CONTRIBUTING.md
+[ctrans]: mailto:chad@transtrum.net
+[dgb]: mailto:donald@traxgame.com
+[env-path]: https://www.npmjs.com/package/env-paths
+[gnutrax]: https://gnutrax.com
+[goldtoken]: https://goldtoken.com/
+[nerdfont]: https://nerdfonts.com/
+[powerline]: https://github.com/powerline/fonts
+[puzzlebook]: https://gnutrax.com/book
+[repo]: https://gitlab.com/slugbugblue/trax-cli
+[sbb]: https://slugbugblue.com/
+[traxbook]: http://traxgame.com/shop_book.php
+[traxgame]: http://traxgame.com/
+[traxhistory]: http://www.traxgame.com/about_history.php
+[traxplayer]: mailto:traxplayer@gmail.com
+[traxrules]: http://www.traxgame.com/about_rules.php
+[xdg]:
+  https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html

package/package.json

@@ -0,0 +1,71 @@
+{
+  "name": "@slugbugblue/trax-cli",
+  "version": "0.11.0",
+  "description": "Trax command line interface",
+  "keywords": [
+    "trax",
+    "traxgame",
+    "cli",
+    "command line interface"
+  ],
+  "homepage": "https://gitlab.com/slugbugblue/trax-cli",
+  "bugs": "https://gitlab.com/slugbugblue/trax-cli/issues",
+  "license": "Apache-2.0",
+  "author": "Chad Transtrum <chad@transtrum.net>",
+  "types": "./src/types.d.ts",
+  "exports": {
+    ".": "./src/cli.js",
+    "./utils": "./src/utils.js",
+    "./version": "./src/version.js",
+    "./version.js": "./src/version.js"
+  },
+  "repository": "gitlab:slugbugblue/trax-cli",
+  "bin": {
+    "trax": "./src/cli.js"
+  },
+  "scripts": {
+    "genversion": "genversion --es6 src/version.js",
+    "git-add": "git add src/version.js benchmark/benchmarks.json",
+    "test": "xo",
+    "prepare": "husky install",
+    "preversion": "npm test",
+    "version": "npm run genversion ; npm run git-add",
+    "postversion": "git push && git push --tags && npm publish"
+  },
+  "dependencies": {
+    "@slugbugblue/trax": "^0.21.0",
+    "@slugbugblue/trax-analyst": "^0.11.0",
+    "@slugbugblue/trax-puzzles": "^0.5.0",
+    "@slugbugblue/trax-tty": "^1.0.0",
+    "env-paths": "^3.0.0",
+    "make-dir": "^3.1.0",
+    "yaml": "^2.0.0-11"
+  },
+  "devDependencies": {
+    "genversion": "^3.0.2",
+    "husky": "^8.0.3",
+    "prettier": "^2.6.1",
+    "xo": "0.*"
+  },
+  "type": "module",
+  "engines": {
+    "node": ">=16.15.0"
+  },
+  "prettier": {
+    "bracketSpacing": true,
+    "proseWrap": "always",
+    "semi": false,
+    "singleQuote": true,
+    "trailingComma": "all",
+    "useTabs": false
+  },
+  "xo": {
+    "prettier": true,
+    "rules": {
+      "curly": [
+        "error",
+        "multi-line"
+      ]
+    }
+  }
+}