* Update Code to 1.94.2
* Convert from yarn to npm
This is to match VS Code. We were already partially using npm for the
releases so this is some nice alignment.
* Update caniuse-lite
This was complaining on every unit test.
* Update eslint
I was having a bunch of dependency conflicts and eslint seemed to be the
culprit so I just removed it and set it up again, since it seems things
have changed quite a bit.
* Update test dependencies
I was getting oom when running the unit tests...updating seems to work.
* Remove package.json `scripts` property in release
The new pre-install script was being included, which is dev-only.
This was always the intent; did not realize jq's merge was recursive.
* Remove jest and devDependencies in release as well
* Update test extension dependencies
This appears to be conflicting with the root dependencies.
* Fix playwright exec
npm does not let you run binaries like yarn does, as far as I know.
* Fix import of server-main.js
* Fix several tests by waiting for selectors
- Remove the redundant title prefix.
- Remove outdated assignees.
- Improve reproduction step description (trying to get folks to submit
more specific/detailed reproductions).
- Render logs with shell (not sure if this actually changes anything).
- Use dropdowns for testing in VS Code and Codespaces. I think the
existing checkboxes are still confusing so hopefully this sorts it.
These checkboxes keep getting checked despite the submitter using an
insecure context or not having tested upstream. I think two things are
at play here:
1. Folks might be interpreting "cannot reproduce" as "did not
reproduce" or "did not have time to reproduce".
2. The checkboxes are required to submit the issue so folks might be
marking them just so they can get their issue submitted; maybe they
are not even reading the checkboxes and are just seeing the error
that they need to be marked and blindly marking them because while
in some cases folks will add "I had to check this but it is not
true", usually they say nothing.
In any case, hopefully these changes make the checkboxes more accurate,
and then if they are unchecked we can ask them to go reproduce in VS
Code or use a secure context or whatever the case may be.
We tried to switch from `yarn` to `npm` because `yarn` ignores lockfiles
but learned that we missed a few key things.
For now, we are reverting docs and a few other changes that suggested
using `npm` instead of `yarn` until we fully remove `yarn` from the
codebase.
t Please enter the commit message for your changes. Lines starting
* docs: update FAQ with extension gallery info (#2672)
* Update app to reflect Open VSX switch.
- Remove extension related github configs.
- Update tests to reflect new upstream behavior.
Co-authored-by: Akash Satheesan <akash@coder.com>
- Most people leave the logs out so add a section for them in the issue
template.
- Remove the VS Code logs because those get sent to stdout now and will
show up in our logs.
- Separate browser console and network.
* Add docs
* Add guides for hosting
* Inital commit. Add quick start guide for self hosted
* Add info for flags
* Detail usage flags and provide examples
* Correct file types for certificate
* Add self-signed certificate guide, update .gitignore
* Add additional information.:
* Checkout to master
* Add transition document, add some links to readme
* Comment out some stuff
* Revise transition document
* Fix typo
* Add Google Cloud setup guide
* fix link
* Add guide links to readme
* Add AWS deployment guide
* Fixup based on PR suggestions
* Fixup ssl guide and readme
* Fix typo
* Add step to make binary executable
* Add digitalocean guide, update readme, add chmod steps just in case
* add information about securing the connection to each deploy guide
* Update doc/security/ssl.md
Co-Authored-By: nol166 <jmccamb@gmail.com>
* Fixup from PR suggestions
* Add guide for systemd for when ssh closes
* Fix typos
* VS Code Remote -> code-server
* Fix minor stylistics
* Update readme (#43)
* Update readme
* Add details about chrome warning
* Add back extension ID settings
* Add back SSL guide to readme
* State that chmod is likely not necessary
* Fix type
* Update readme
* Remove transition guide
* Revise readme based on suggestions. (#45)
* Update references to vscode-remote
* No Windows support yet
Olivier Benz