* Fix acquisition error on non fully qualified version
The new, unreleased code for getting a feature band of a sdk version try catches when it tries to get the band. It will not throw if there is no band in the string which can be expected in certain cases, but it still posts an error to the event stream. Posting an error to the event stream causes the error to bubble up to the user even if it is caught. We need to take some additional action here so the user doesn't see an error popup for something that's not an error. This is blocking our release with all of the findPath features.
Resolves https://github.com/dotnet/vscode-dotnet-runtime/issues/2015
Version updates are to update the shas of the internal packages which got updated.
* Update imports
* remove extra else
* get eslint running but its failing a lot of checks
* Fix the linting after migration
* Fix many errors
* 65 errors to go
* fix almost every lint issue
* clean lint
* Remove references to tslint
* dont install eslint as it is already here
* install eslint
* update eslint
* dont empty cache because eslint is failing to register the types that exist
* try to help eslint find the files for type defs
* Set typescript resolver
* Fix imports
* Add some import plugin but still cant import vscode correctly
* install eslint globally
* skip npm installl
* add imports
* try to fix the import issue
* build before hand so the types are picked up -_____-
* Revert "build before hand so the types are picked up -_____-"
This reverts commit e5381b42df.
* rollback to eslint 8 but still run build
* Update axios cache interceptor for bug fix
* Force update axios as well
* Migrate from vsce to @vscode/vsce
This is required for using newer versions of vsce.
* Update Node to 18 from 16 as VSCE now requires 18
* Extend log test timeout since it seems to sometimes take longer
* Make the assert not a question
* Update Dependencies
* Remove is online
Is-online now requires ES6.
It has not been maintained in over 2 years.
The checks it does are fairly rudimentary. We only rely on this code to try to diagnose the error which has already happened.
I would trust this code rather than rely on external libraries.
* Fix timeout logic for no is online
* Fix Linting Issues
Add to the local SDK tests that fail if you have a global SDK a warning so they dont fail when building on a devbox
Merge in the version resolver changes to expect a json object from WRWorker
Merge all of the package upgrades together
VSCode added support for no activiation events in vsce with 1.74.0, the vsce package will fail until this update was added to bump vscode engine in the sample extension. VSCE is also deprecated and you must use @vscode/vsce now.
Noah Gilson
Noah Gilson