add a defer/recover to scws WriteJson

* various improvements

* animation menu on close

* finish custom dropdown

* minor change

* minor fix

* add error support for dropdown

* create remote modal

* NumberField component and more on add remote connection modal implementation

* extend TextField instead. dobounce should be handled by the user not the component

* PasswordField

* remove used code. fix ssh key file field issue

* style buttons. fix modal height issue

* use react portal for dropdown menu

* remove debugging code

* tooltip implementation

* put back modal background

* (sawka) add autofocus attribute to textfield.  change label color to color-secondary.  fix file menu name.  fix typescript error in basicrenderer

.gitignore

@@ -3,13 +3,20 @@ dist-dev/
 node_modules/
 *~
 *.log
+*.out
 out/
 .DS_Store
 bin/
+waveshell/bin/
+wavesrv/bin/
 dev-bin
 local-server-bin
 *.pw
 build/
 *.dmg
 webshare/dist/
-webshare/dist-dev/
+webshare/dist-dev/
+temp.sql
+.idea/
+test/
+.vscode/

BUILD.md

@@ -0,0 +1,79 @@
+# Build Instructions for Wave Terminal
+
+These instructions are for setting up the build on MacOS. 
+If you're developing on Linux please use the [Linux Build Instructions](./build-linux.md).
+
+## Running the Development Version of Wave
+
+If you install the production version of Wave, you'll see a semi-transparent sidebar, and the data for Wave is stored in the directory ~/prompt.  The development version has a red/brown sidebar and stores its data in ~/prompt-dev.  This allows the production and development versions to be run simultaneously with no conflicts.  If the dev database is corrupted by development bugs, or the schema changes in development it will not affect the production copy.
+
+## Prereqs and Tools
+
+Download and install Go (must be at least go 1.18):
+```
+brew install go
+```
+
+Download and install ScriptHaus (to run the build commands):
+```
+brew tap scripthaus-dev/scripthaus
+brew install scripthaus
+```
+
+You also need a relatively modern nodejs with npm and yarn installed.
+   * Node can be installed from [https://nodejs.org](https://nodejs.org).  
+   * npm can install yarn using: 
+
+```
+npm install -g yarn
+```
+
+## Clone the Repo
+
+```
+git clone git@github.com:wavetermdev/waveterm.git
+```
+
+## Building WaveShell / WaveSrv
+
+```
+scripthaus run build-backend
+```
+
+This builds the Golang backends for Wave.  The binaries will put in waveshell/bin and wavesrv/bin respectively.  If you're working on a new plugin or other pure frontend changes to Wave, you won't need to rebuild these unless you pull new code from the Wave Repository.
+
+## One-Time Setup
+
+Install modules (we use yarn):
+```
+yarn
+```
+
+Electron also requires specific builds of node_modules to work (because Electron embeds a specific node.js version that might not match your development node.js version).  We use a special electron command to cross-compile those modules:
+
+```
+scripthaus run electron-rebuild
+```
+
+## Running WebPack
+
+We use webpack to build both the React and Electron App Wrapper code.  They are both run together using:
+
+```
+scripthaus run webpack-watch
+```
+
+## Running the WaveTerm Dev Client
+
+Now that webpack is running (and watching for file changes) we can finally run the WaveTerm Dev Client!  To start the client run:
+```
+scripthaus run electron
+```
+
+To kill the client, either exit the Electron App normally or just Ctrl-C the ```scripthaus run electron``` command.
+
+Because we're running webpack in watch mode, any changes you make to the typescript will be automatically picked up by the client after a refresh.  Note that I've disabled hot-reloading in the webpack config, so to pick up new changes you'll have to manually refresh the WaveTerm Client window.  To do that use "Command-Shift-R" (Command-R is used internally by WaveTerm and will not force a refresh).
+
+## Debugging the Dev Client
+
+You can use the regular Chrome DevTools to debug the frontend application.  You can open the DevTools using the keyboard shortcut `Cmd-Option-I`.

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+coc@commandline.dev.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -0,0 +1,47 @@
+# Contributing to Wave Terminal 
+
+We welcome and value contributions to Wave Terminal! Wave is an open source project, always open for contributors. There are several ways you can contribute:
+   * Submit issues related to bugs or new feature requests
+   * Fix outstanding [issues](https://github.com/wavetermdev/waveterm/issues) with the existing code
+   * Contribute to [documentation](https://github.com/wavetermdev/waveterm-docs)
+   * Spread the word on social media (tag us on [LinkedIn](https://www.linkedin.com/company/commandlinedev), [Twitter/X](https://twitter.com/commandlinedev))
+   * Or simply ⭐️ the repository to show your appreciation
+
+However you choose to contribute, please be mindful and respect our [code of conduct](./CODE_OF_CONDUCT.md).
+
+> All contributions are highly appreciated! 🥰
+
+## Before You Start
+We accept patches in the form of github pull requests. If you are new to github, please review this [github pull request guide](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
+
+### Contributor License Agreement
+Contributions to this project must be accompanied by a Contributor License Agreement (CLA). You (or your employer) retain the copyright to your contribution, this simply gives us permission to use and redistribute your contributions as part of the project. 
+
+> On submission of your first pull request you will be prompted to sign the CLA confirming your original code contribution and that you own the intellectual property. 
+
+### Style guide
+The project uses American English. 
+
+Coding style and formatting is automated for each pull request. We use [Prettier](https://prettier.io/).
+
+## How to contribute
+
+  * For minor changes, you are welcome to [open a pull request](https://github.com/wavetermdev/waveterm/pulls). 
+  * For major changes, please [create an issue](https://github.com/wavetermdev/waveterm/issues/new) first.
+  * If you are looking for a place to start take a look at [open issues](https://github.com/wavetermdev/waveterm/issues).
+  * Join the [Discord channel](https://discord.gg/XfvZ334gwU) to collaborate with the community on your contribution.
+
+
+### Development Environment
+
+To build and run wave term locally see instructions below:
+   * [MacOS build instructions](./BUILD.md)
+   * [Linux build instructions](./build-linux.md)
+
+### Create a Pull Request
+
+Guidelines:
+   * Before writing any code, please look through existing PRs or issues to make sure nobody is already working on the same thing. 
+   * Develop features on a branch - do not work on the main branch
+   * For anything but minor fixes, please submit tests and documentation
+   * Please reference the issue in the pull request

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 [yyyy] [name of copyright owner]
+
+   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.

NOTICE

@@ -0,0 +1 @@
+Copyright 2023, Command Line Inc.

README.md

@@ -0,0 +1,50 @@
+
+<p align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="./src/app/assets/wave-logo_horizontal-coloronblack.svg">
+    <source media="(prefers-color-scheme: light)" srcset="./src/app/assets/wave-logo_horizontal-coloronwhite.svg">
+    <img alt="Wave Terminal Logo" src="./src/app/assets/wave-logo_horizontal-coloronwhite.svg" width="352" height="59" style="max-width: 100%;">
+  </picture>
+  <br/>
+</p>
+
+# Wave Terminal 
+
+A open-source, cross-platform, modern terminal for seamless workflows.
+
+Wave isn't just another terminal emulator; it's a rethink on how terminals are built.  Wave combines command line with the power of the open web to help veteran CLI users and new developers alike.
+
+* Inline renderers to cut down on context switching.  Render code, images, markdown, and CSV files without ever leaving the terminal.
+* Persistent sessions that can restore state across network disconnections and reboots
+* Searchable contextual command history across all remote sessions (saved locally)
+* Workspaces, tabs, and command blocks to keep you organized
+
+## Installation
+
+Wave Terminal works with MacOS and Linux (preliminary).
+
+Install Wave Terminal from: [www.waveterm.dev/download](https://www.waveterm.dev/download)
+
+## Links
+
+* Homepage &mdash; https://www.waveterm.dev
+* Download Page &mdash; https://www.waveterm.dev/download
+* Documentation &mdash; https://docs.waveterm.dev/
+* Quick Start Guide &mdash; https://docs.waveterm.dev/quickstart/
+* Discord Community &mdash; https://discord.gg/XfvZ334gwU
+
+## Building from Source
+
+* [MacOS Build Instructions](./BUILD.md)
+* [Linux Build Instructions](./build-linux.md)
+
+## Contributing
+
+Wave uses Github Project for tracking issues. 
+
+Find more information in our [Contributions Guide](CONTRIBUTING.md), which includes:
+
+  * [Ways to contribute](CONTRIBUTING.md#contributing-to-wave-terminal)
+  * [Contribution guidelines](CONTRIBUTING.md#before-you-start)
+
+

SECURITY.md

@@ -0,0 +1,5 @@
+## Reporting Security Issues
+
+To report vulnerabilities or security concerns, please email us at: [security@commandline.dev](mailto:security@commandline.dev)
+
+** Please do not report security vulnerabilities through public github issues. **

build-linux.md

@@ -0,0 +1,108 @@
+# Build Instructions for Wave Terminal on Linux
+
+These instructions are for setting up the build on Linux (Ubuntu). 
+If you're developing on MacOS please use the [MacOS Build Instructions](./BUILD.md).
+If you are working on a different Linux distribution, you may need to adapt some of these instructions to fit your environment.
+
+## Running the Development Version of Wave
+
+If you install the production version of Wave, you'll see a semi-transparent sidebar, and the data for Wave is stored in the directory ~/prompt.  The development version has a red/brown sidebar and stores its data in ~/prompt-dev.  This allows the production and development versions to be run simultaneously with no conflicts.  If the dev database is corrupted by development bugs, or the schema changes in development it will not affect the production copy.
+
+## Prereqs and Tools
+
+Download and install Go (must be at least go 1.18).  We also need gcc installed to run a CGO build (for Golang).
+zip is required to build linux deployment packages (not required for running and debugging dev builds).
+
+```
+sudo snap install go --classic
+sudo apt-get update
+sudo apt-get install gcc
+sudo apt-get install zip
+```
+
+Download and install [ScriptHaus](https://github.com/scripthaus-dev/scripthaus) (to run the build commands):
+
+```
+git clone https://github.com/scripthaus-dev/scripthaus.git
+cd scripthaus
+CGO_ENABLED=1 go build -o scripthaus cmd/main.go
+```
+
+You'll now have to move the built `scripthaus` binary to a directory in your path (e.g. /usr/local/bin):
+
+```
+sudo cp scripthaus /usr/local/bin
+```
+
+## Install nodejs, npm, and yarn
+
+We use [nvm](https://github.com/nvm-sh/nvm) to install nodejs on Linux (you can use an alternate installer if you wish).  You must have a relatively recent version of node in order to build the terminal.  Different distributions and shells will require different setup instructions.  These instructions work for Ubuntu 22 using bash (will install node v20.8.1):
+
+```
+wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.5/install.sh | bash
+source ~/.bashrc
+nvm install v20.8.1
+```
+
+Now we can install yarn:
+
+```
+npm install -g yarn
+```
+
+
+## Clone the Wave Repo
+
+Move out of the `scripthaus` directory if you're still in it.  Clone the wave repository into the directory that you'd like to use for development.
+
+```
+git clone git@github.com:wavetermdev/waveterm.git
+```
+
+## One-Time Setup
+
+Install Wave modules (we use yarn):
+```
+yarn
+```
+
+Electron also requires specific builds of node_modules to work (because Electron embeds a specific node.js version that might not match your development node.js version).  We use a special electron command to cross-compile those modules:
+
+```
+scripthaus run electron-rebuild
+```
+
+## Building WaveShell / WaveSrv
+
+cd into the waveterm directory (if you haven't already) and run the build-backend command using `scripthaus`.
+
+```
+cd waveterm
+scripthaus run build-backend
+```
+
+This builds the Golang backends for Wave.  The binaries will put in waveshell/bin and wavesrv/bin respectively.  If you're working on a new plugin or other pure frontend changes to Wave, you won't need to rebuild these unless you pull new code from the Wave Repository.
+
+
+## Running WebPack
+
+We use webpack to build both the React and Electron App Wrapper code.  They are both run together using:
+
+```
+scripthaus run webpack-watch
+```
+
+## Running the WaveTerm Dev Client
+
+Now that webpack is running (and watching for file changes) we can finally run the WaveTerm Dev Client!  To start the client run:
+```
+scripthaus run electron
+```
+
+To kill the client, either exit the Electron App normally or just Ctrl-C the ```scripthaus run electron``` command.
+
+Because we're running webpack in watch mode, any changes you make to the typescript will be automatically picked up by the client after a refresh.  Note that I've disabled hot-reloading in the webpack config, so to pick up new changes you'll have to manually refresh the WaveTerm Client window.  To do that use "Command-Shift-R" (Command-R is used internally by Wave and will not force a refresh).
+
+## Debugging the Dev Client
+
+You can use the regular Chrome DevTools to debug the frontend application.  You can open the DevTools using the keyboard shortcut `Cmd-Option-I`.

buildres/.gitignore

@@ -0,0 +1,3 @@
+temp/
+*.zip
+*.dmg

buildres/build-universal.js

@@ -0,0 +1,20 @@
+const eu = require("@electron/universal");
+const path = require("path");
+
+let x64Path = path.resolve(__dirname, "temp", "x64", "Wave.app")
+let arm64Path = path.resolve(__dirname, "temp", "arm64", "Wave.app")
+let outPath = path.resolve(__dirname, "temp", "Wave.app")
+
+console.log("building universal package");
+console.log("x64 path", x64Path);
+console.log("arm64 path", arm64Path);
+console.log("output path", outPath);
+
+(async () => {
+    await eu.makeUniversalApp({
+        x64AppPath: x64Path,
+        arm64AppPath: arm64Path,
+        outAppPath: outPath,
+    });
+    console.log("created macos universal app");
+})();

buildres/build-universal.sh

@@ -0,0 +1,51 @@
+#!/bin/bash
+
+# assumes we have Wave-darwin-x64-[version].zip and Wave-darwin-arm64-[version].zip in current directory
+VERSION=0.5.0
+rm -rf temp
+mkdir temp
+mkdir temp/x64
+X64_ZIP="Wave-darwin-x64-$VERSION.zip"
+ARM64_ZIP="Wave-darwin-arm64-$VERSION.zip"
+if ! [ -f $X64_ZIP ]; then
+    echo "no $X64_ZIP found";
+    exit 1;
+fi
+if ! [ -f $ARM64_ZIP ]; then
+    echo "no $ARM64_ZIP found"
+    exit 1;
+fi
+set -e
+echo "unzipping version v$VERSION zip files"
+ls -l "$X64_ZIP" "$ARM64_ZIP"
+unzip -q $X64_ZIP -d temp/x64
+mkdir temp/arm64
+unzip -q $ARM64_ZIP -d temp/arm64
+lipo -create -output temp/wavesrv temp/x64/Wave.app/Contents/Resources/app/bin/wavesrv temp/arm64/Wave.app/Contents/Resources/app/bin/wavesrv
+rm -rf temp/arm64/Wave.app/Contents/Resources/app
+mv temp/x64/Wave.app/Contents/Resources/app temp/
+cp temp/wavesrv temp/app/bin/wavesrv
+mkdir temp/x64/Wave.app/Contents/Resources/app
+mkdir temp/arm64/Wave.app/Contents/Resources/app
+node build-universal.js
+rm -rf temp/Wave.app/Contents/Resources/app
+mv temp/app temp/Wave.app/Contents/Resources/app
+node osx-sign.js
+DEBUG=electron-notarize node osx-notarize.js
+echo "universal app creation success (build/sign/notarize)"
+echo "creating universal dmg"
+rm -f *.dmg
+DMG_VERSION=$(node -e 'console.log(require("../version.js"))')
+DMG_NAME="waveterm-macos-universal-${DMG_VERSION}.dmg"
+../../create-dmg/create-dmg \
+  --volname "WaveTerm" \
+  --window-pos 200 120 \
+  --window-size 600 300 \
+  --icon-size 100 \
+  --icon "Wave.app" 200 130 \
+  --hide-extension "Wave.app" \
+  --app-drop-link 400 125 \
+  $DMG_NAME \
+  "temp/Wave.app"
+echo "success, created $DMG_NAME"
+spctl -a -vvv -t install temp/Wave.app/

buildres/osx-notarize.js

@@ -0,0 +1,14 @@
+const { notarize } = require('@electron/notarize');
+// DEBUG=electron-notarize
+
+console.log("running osx-notarize");
+notarize({
+    appPath: "temp/Wave.app",
+    tool: "notarytool",
+    keychainProfile: "notarytool-creds",
+}).then(() => {
+    console.log("notarize success");
+}).catch((e) => {
+    console.log("notarize error", e);
+    process.exit(1);
+});

buildres/osx-sign.js

@@ -0,0 +1,20 @@
+const { signAsync } = require("@electron/osx-sign");
+// DEBUG="electron-osx-sign*"
+
+console.log("running osx-sign");
+let waveAppPath = "temp/Wave.app";
+signAsync({
+    app: "temp/Wave.app",
+    binaries: [
+        waveAppPath + "/Contents/Resources/app/bin/wavesrv",
+        waveAppPath + "/Contents/Resources/app/bin/mshell/mshell-v0.3-linux.amd64",
+        waveAppPath + "/Contents/Resources/app/bin/mshell/mshell-v0.3-linux.arm64",
+        waveAppPath + "/Contents/Resources/app/bin/mshell/mshell-v0.3-darwin.amd64",
+        waveAppPath + "/Contents/Resources/app/bin/mshell/mshell-v0.3-darwin.arm64",
+    ],
+}).then(() => {
+    console.log("signing success");
+}).catch((e) => {
+    console.log("signing error", e);
+    process.exit(1);
+});

buildres/universal.md

@@ -0,0 +1,50 @@
+## MacOS Universal Build Notes
+
+This doesn't work out of the box and doesn't seem to be well documented anywhere.
+The basic idea is that we have to create separate x64 and a arm64 builds and
+then link them together using @electron/universal.  Seems easy, but in
+practice it isn't.
+
+(1) The separate x64 and arm64 builds *cannot* be signed (osx-sign).  This
+makes sense because once we lipo the executables together they need to be
+resigned (their SHA sums will change).  If you accidentally sign them
+@electron/universal will also refuse to work.
+
+(2) We already deal with architecture specific builds with Go for wavesrv and
+waveshell.  This upsets @electron/universal as well since these are *binaries*
+and we don't want to lipo them together.
+
+(3) Small differences in waveterm.js.  The non-executable files must be
+*identical*.  Well, that's a problem when we inject build times into the files.
+Other small differences can also happen (like different go toolchains, etc.).
+
+(4) ASAR builds.  By default if there are differences in the "app" folder
+@electron/universal plays some neat tricks to separate out the x64 from the
+arm64 code using a app.asar stub.  That's great for standard electron builds
+where the entrypoint is hardcoded to index.js.  Ours isn't so this doesn't work.
+
+(5) ASAR builds and unpacked files.  I don't know all the details here, but
+for Wave to work we have to have some files unpacked (not in ASAR format).
+The reason is that we execute them directly (e.g. wavesrv and waveshell), they
+aren't just loaded by electron.
+
+(6) Ignoring and skipping files in @electron/universal is hard because
+it just takes one minimatch pattern.
+
+---
+
+## Solution
+
+1. Create unsigned builds on x64 and arm64
+2. Move the builds to the core build machine and *extract* their "app" directories.
+In theory because we aren't using any native node modules they function the same in
+both environments.
+3. Run @electron/universal on the two unsigned builds (without their app directories).
+4. lipo wavesrv from x64 and arm64 manually to create a universal wavesrv binary.
+5. Copy our extracted "app" directory (with the newly created universal "wavesrv")
+back into the universal Wave.app created by @electron/universal.
+6. Manually run osx-sign to sign the new universal build (make sure to
+pass the wavesrv and waveshell programs as extra binaries).
+7. Manually create the new universal dmg (using create-dmg).
+
+

forge.config.js

@@ -7,9 +7,6 @@ var AllowedFirstParts = {
 };
 
 var AllowedNodeModules = {
-    // "lzma-native": true,
-    // "fs-ext": true,
-    // "fsevents": true,
     "monaco-editor": true,
 };
 
@@ -40,6 +37,9 @@ function ignoreFn(path) {
         if (!AllowedNodeModules[nodeModule]) {
             return true;
         }
+        if (nodeModule == "monaco-editor" && parts.length >= 4 && parts[3] != "min") {
+            return true;
+        }
     }
     return false;
 }
@@ -51,44 +51,14 @@ module.exports = {
             "package.json",
             "dist/*",
             "public/*",
-            "node_modules/lzma-native/**",
-            "node_modules/fs-ext/**",
-            "node_modules/fsevents/**",
         ],
-        icon: "public/Prompt.icns",
-        osxNotarize: {
-            tool: "notarytool",
-            keychainProfile: "notarytool-creds",
-        },
-        osxSign: {
-            "hardened-runtime": true,
-            binaries: [
-                "Contents/Resources/app/bin/prompt-local-server",
-                "Contents/Resources/app/bin/mshell/mshell-v0.2-linux.amd64",
-                "Contents/Resources/app/bin/mshell/mshell-v0.2-linux.arm64",
-                "Contents/Resources/app/bin/mshell/mshell-v0.2-darwin.amd64",
-                "Contents/Resources/app/bin/mshell/mshell-v0.2-darwin.arm64",
-            ],
-            identity: "VYQ48YC2N2",
-        },
+        icon: "public/waveterm.icns",
     },
     rebuildConfig: {},
     makers: [
-        {
-            name: "@electron-forge/maker-squirrel",
-            config: {},
-        },
         {
             name: "@electron-forge/maker-zip",
-            platforms: ["darwin"],
-        },
-        {
-            name: "@electron-forge/maker-deb",
-            config: {},
-        },
-        {
-            name: "@electron-forge/maker-rpm",
-            config: {},
+            platforms: ["darwin", "linux"],
         },
     ],
 };

go.work

@@ -0,0 +1,4 @@
+go 1.18
+
+use ./wavesrv
+use ./waveshell

go.work.sum

@@ -0,0 +1,6 @@
+github.com/yuin/goldmark v1.4.13/go.mod h1:6yULJ656Px+3vBD8DxQVa3kxgyrAnzto9xy5taEt/CY=
+golang.org/x/net v0.10.0/go.mod h1:0qNGK6F8kojg2nk9dLZ2mShWaEBan6FAoqfSigmmuDg=
+golang.org/x/sync v0.2.0/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
+golang.org/x/sys v0.8.0/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
+golang.org/x/tools v0.1.12/go.mod h1:hNGJHUnrk76NpqgfD5Aqm5Crs+Hm0VOH/i9J2+nxYbc=
+golang.org/x/tools v0.9.1/go.mod h1:owI94Op576fPu3cIGQeHs3joujW/2Oc6MtlxbF5dfNc=

housekeeping/wave-migrate.sh

@@ -0,0 +1,17 @@
+#!/bin/bash
+
+if [ ! -d ~/prompt ]; then
+    echo "~/prompt directory does not exist, will not migrate"
+    exit 1;
+fi
+if [ -d ~/.waveterm ]; then
+    echo "~/.wave directory already exists, will not migrate"
+    exit 1;
+fi
+mv ~/prompt ~/.waveterm
+mv ~/.waveterm/prompt.db     ~/.waveterm/waveterm.db
+mv ~/.waveterm/prompt.db-wal ~/.waveterm/waveterm.db-wal
+mv ~/.waveterm/prompt.db-shm ~/.waveterm/waveterm.db-shm
+mv prompt.authkey waveterm.authkey
+
+