vscode/test/smoke/package.json
Connor Peet 2138622b04
build: add watch/compile tasks for CLI (#182344)
* build: add watch/compile tasks for CLI

I spent time this morning working on the 'developer experience' of the
CLI in vscode, mainly getting the CLI to cross-compile chasing our
initial idea of having it auto-build in a devcontainer.

After some effort and disabling tunnels connections (to avoid having to
pull in OpenSSL which is a huge pain to cross compile), I was able to
get it to cross-compile from Linux to Windows, using the mingw linker.
I could probably figure out how to get macOS working as well with more
effort. However, I'm not a big fan of this, effectively it's one more
'platform' of build we need to support and test.

I think a better approach is downloading the latest compiled CLI from
the update server instead, as needed. That's what this PR does. It just
places the CLI where it _would_ normally get compiled to by cargo; so
far we don't need to do anything special outside of that.
A notice is shown to users if this fallback happens.

* update from review
2023-06-20 14:34:11 -07:00

31 lines
911 B
JSON

{
"name": "code-oss-dev-smoke-test",
"version": "0.1.0",
"license": "MIT",
"main": "./src/main.js",
"scripts": {
"compile": "yarn --cwd ../automation compile && node ../../node_modules/typescript/bin/tsc",
"watch-automation": "yarn --cwd ../automation watch",
"watch-smoke": "node ../../node_modules/typescript/bin/tsc --watch --preserveWatchOutput",
"watch": "npm-run-all -lp watch-automation watch-smoke",
"mocha": "node ../node_modules/mocha/bin/mocha"
},
"dependencies": {
"@vscode/test-electron": "^2.3.2",
"mkdirp": "^1.0.4",
"ncp": "^2.0.0",
"node-fetch": "^2.6.7",
"rimraf": "3.0.2"
},
"devDependencies": {
"@types/mkdirp": "^1.0.1",
"@types/mocha": "^9.1.1",
"@types/ncp": "2.0.1",
"@types/node": "16.x",
"@types/node-fetch": "^2.5.10",
"@types/rimraf": "3.0.2",
"npm-run-all": "^4.1.5",
"watch": "^1.0.2"
}
}