Open virzak opened 4 months ago
All your points are valid.
There's a lot of complexity, and some of it is beyond the essential complexity, out into accidental complexity territory.
It looks like I need to update the local testing process and documentation.
Originally the locally-generated installers were network-free, but a few months back I made some changes that inadvertently require network access to give some non-essential information - such as the current version of the software.
Rather than invest the time into solving that specific problem, I'd rather move forward with the roadmap to move the install process away from plugin-style functions and towards template generated installers.
... but I don't think I'm in a good place to dedicate that much time to it... so maybe the former is the better option.
I'm trying to contribute to the repo, but was unable to find a way to do that.
Here are the steps I took:
How do I test before committing?
I tried to start Live Preview. I then changed the URL to
curl -sS https://super-duper-rotary-phone-p66x959p45397g-3000.app.github.dev/shfmt | sh
, but the result I got back was HTML.There is some sort of url handler, but I have no idea how to invoke it.
The next thing I tried was
yarn start
andnpm start
hoping it would be easy to start a server with proper URL handling, but that was missing also.Then i read more documentation and after realizing that
packages
were renamed towebi-installers
ran the following:The clone command needs to include submodules. Alternatively they should be brought in later if, for example, git clone was donw by codespaces
On one of my machines I've been getting:
I needed to disable that line.
Now the message I'm getting is:
Perhaps it is my fault, but it took me a while to realize that the script actually created new files in the root directory.
Turns out it generated:
Setting the variable before running node didn't help either, so I overwrote it manually.
Now I have a few options:
Installing pwsh ... Found ~/.local/bin