code-server/package.json

71 lines
2.1 KiB
JSON
Raw Normal View History

2019-01-08 08:46:19 +08:00
{
"name": "@coder/code-server",
"repository": "https://github.com/codercom/code-server",
2019-01-08 08:46:19 +08:00
"author": "Coder",
2019-02-06 04:56:02 +08:00
"license": "MIT",
2019-02-06 05:26:57 +08:00
"description": "Run VS Code remotely.",
2019-01-08 08:46:19 +08:00
"scripts": {
"build:rules": "cd ./rules && tsc -p .",
"packages:install": "cd ./packages && yarn",
"postinstall": "npm-run-all --parallel packages:install build:rules",
"start": "cd ./packages/server && yarn start",
"task": "ts-node -r tsconfig-paths/register build/tasks.ts",
2019-01-08 08:46:19 +08:00
"test": "cd ./packages && yarn test"
},
"devDependencies": {
"@types/fs-extra": "^5.0.4",
2019-01-12 01:49:56 +08:00
"@types/node": "^10.12.18",
"@types/tar": "^4.0.0",
2019-02-08 01:05:17 +08:00
"@types/trash": "^4.3.1",
"cache-loader": "^2.0.1",
"cross-env": "^5.2.0",
2019-01-12 08:11:34 +08:00
"crypto-browserify": "^3.12.0",
"css-loader": "^2.1.0",
"file-loader": "^3.0.1",
"fork-ts-checker-webpack-plugin": "^0.5.2",
"fs-extra": "^7.0.1",
2019-01-12 08:11:34 +08:00
"happypack": "^5.0.1",
"html-webpack-plugin": "^3.2.0",
"http-browserify": "^1.7.0",
"ignore-loader": "^0.1.2",
2019-01-12 08:11:34 +08:00
"mini-css-extract-plugin": "^0.5.0",
2019-01-12 02:58:25 +08:00
"node-sass": "^4.11.0",
2019-01-12 01:49:56 +08:00
"npm-run-all": "^4.1.5",
Make everything use active evals (#30) * Add trace log level * Use active eval to implement spdlog * Split server/client active eval interfaces Since all properties are *not* valid on both sides * +200% fire resistance * Implement exec using active evaluations * Fully implement child process streams * Watch impl, move child_process back to explicitly adding events Automatically forwarding all events might be the right move, but wanna think/discuss it a bit more because it didn't come out very cleanly. * Would you like some args with that callback? * Implement the rest of child_process using active evals * Rampant memory leaks Emit "kill" to active evaluations when client disconnects in order to kill processes. Most likely won't be the final solution. * Resolve some minor issues with output panel * Implement node-pty with active evals * Provide clearTimeout to vm sandbox * Implement socket with active evals * Extract some callback logic Also remove some eval interfaces, need to re-think those. * Implement net.Server and remainder of net.Socket using active evals * Implement dispose for active evaluations * Use trace for express requests * Handle sending buffers through evaluation events * Make event logging a bit more clear * Fix some errors due to us not actually instantiating until connect/listen * is this a commit message? * We can just create the evaluator in the ctor Not sure what I was thinking. * memory leak for you, memory leak for everyone * it's a ternary now * Don't dispose automatically on close or error The code may or may not be disposable at that point. * Handle parsing buffers on the client side as well * Remove unused protobuf * Remove TypedValue * Remove unused forkProvider and test * Improve dispose pattern for active evals * Socket calls close after error; no need to bind both * Improve comment * Comment is no longer wishy washy due to explicit boolean * Simplify check for sendHandle and options * Replace _require with __non_webpack_require__ Webpack will then replace this with `require` which we then provide to the vm sandbox. * Provide path.parse * Prevent original-fs from loading * Start with a pid of -1 vscode immediately checks the PID to see if the debug process launch correctly, but of course we don't get the pid synchronously. * Pass arguments to bootstrap-fork * Fully implement streams Was causing errors because internally the stream would set this.writing to true and it would never become false, so subsequent messages would never send. * Fix serializing errors and streams emitting errors multiple times * Was emitting close to data * Fix missing path for spawned processes * Move evaluation onDispose call Now it's accurate and runs when the active evaluation has actually disposed. * Fix promisifying fs.exists * Fix some active eval callback issues * Patch existsSync in debug adapter
2019-02-20 00:17:03 +08:00
"path-browserify": "^1.0.0",
2019-01-12 08:11:34 +08:00
"preload-webpack-plugin": "^3.0.0-beta.2",
"sass-loader": "^7.1.0",
"string-replace-loader": "^2.1.1",
2019-01-12 08:11:34 +08:00
"style-loader": "^0.23.1",
"tar": "^4.4.8",
"terser-webpack-plugin": "^1.2.3",
2019-01-12 08:11:34 +08:00
"ts-loader": "^5.3.3",
"ts-node": "^7.0.1",
"tsconfig-paths": "^3.8.0",
"tslib": "^1.9.3",
"tslint": "^5.12.1",
2019-01-12 08:11:34 +08:00
"typescript": "^3.2.2",
"typescript-tslint-plugin": "^0.2.1",
2019-01-12 08:11:34 +08:00
"uglifyjs-webpack-plugin": "^2.1.1",
"url-loader": "^1.1.2",
"util": "^0.11.1",
2019-01-12 08:11:34 +08:00
"webpack": "^4.28.4",
"webpack-bundle-analyzer": "^3.0.3",
"webpack-cli": "^3.2.1",
"webpack-dev-middleware": "^3.5.0",
2019-01-12 08:11:34 +08:00
"webpack-dev-server": "^3.1.14",
"webpack-hot-middleware": "^2.24.3",
"webpack-pwa-manifest": "^4.0.0",
"workbox-webpack-plugin": "^4.1.0",
2019-01-12 08:11:34 +08:00
"write-file-webpack-plugin": "^4.5.0"
},
"resolutions": {
"bindings": "1.3.0"
},
"dependencies": {
"node-loader": "^0.6.0",
"node-pty": "0.8.1",
"spdlog": "0.8.1",
"webpack-merge": "^4.2.1"
2019-01-08 08:46:19 +08:00
}
}