cubetiq/code-server
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
1.604-vsc1.32.0
code-server/packages/package.json

49 lines
1.2 KiB
JSON
Raw Permalink Normal View History

not finished
2019-01-08 07:46:19 +07:00
{
"scripts": {
Getting the client to run (#12) * Clean up workbench and integrate initialization data * Uncomment Electron fill * Run server & client together * Clean up Electron fill & patch * Bind fs methods This makes them usable with the promise form: `promisify(access)(...)`. * Add space between tag and title to browser logger * Add typescript dep to server and default __dirname for path * Serve web files from server * Adjust some dev options * Rework workbench a bit to use a class and catch unexpected errors * No mkdirs for now, fix util fill, use bash with exec * More fills, make general client abstract * More fills * Fix cp.exec * Fix require calls in fs fill being aliased * Create data and storage dir * Implement fs.watch Using exec for now. * Implement storage database fill * Fix os export and homedir * Add comment to use navigator.sendBeacon * Fix fs callbacks (some args are optional) * Make sure data directory exists when passing it back * Update patch * Target es5 * More fills * Add APIs required for bootstrap-fork to function (#15) * Add bootstrap-fork execution * Add createConnection * Bundle bootstrap-fork into cli * Remove .node directory created from spdlog * Fix npm start * Remove unnecessary comment * Add webpack-hot-middleware if CLI env is not set * Add restarting to shared process * Fix starting with yarn
2019-01-19 04:46:40 +07:00
"postinstall": "../node_modules/.bin/ts-node ../scripts/install-packages.ts",
not finished
2019-01-08 07:46:19 +07:00
"test": "jest"
},
"devDependencies": {
"@types/jest": "^23.3.12",
"jest": "^23.6.0",
Implement fs module (#3) * Implements the fs module * Add stats object * Add not implemented to createWriteStream * Update mkdtemp to use tmp dir * Unexport Stats * Add client web socket for commands and restructure
2019-01-15 03:58:34 +07:00
"ts-jest": "^23.10.5"
not finished
2019-01-08 07:46:19 +07:00
},
"dependencies": {
"xmlhttprequest": "1.8.0"
},
"jest": {
Fix install from VSIX for TAR and ZIP formats (#245) * Fix install from VSIX for TAR and ZIP formats * Parse TAR before ZIP, when installing from VSIX
2019-03-22 02:04:09 +07:00
"globals": {
"ts-jest": {
"diagnostics": false
}
},
not finished
2019-01-08 07:46:19 +07:00
"moduleFileExtensions": [
"ts",
"tsx",
"js",
"json"
],
"setupFiles": [
Implement fs module (#3) * Implements the fs module * Add stats object * Add not implemented to createWriteStream * Update mkdtemp to use tmp dir * Unexport Stats * Add client web socket for commands and restructure
2019-01-15 03:58:34 +07:00
"<rootDir>/../scripts/test-setup.js"
not finished
2019-01-08 07:46:19 +07:00
],
"moduleNameMapper": {
Implement fs module (#3) * Implements the fs module * Add stats object * Add not implemented to createWriteStream * Update mkdtemp to use tmp dir * Unexport Stats * Add client web socket for commands and restructure
2019-01-15 03:58:34 +07:00
"^.+\\.(s?css|png|svg)$": "<rootDir>/../scripts/dummy.js",
Move and refactor child_process tests
2019-02-20 04:30:56 +07:00
"@coder/ide/src/fill/evaluation": "<rootDir>/ide/src/fill/evaluation",
Move node-pty tests
2019-02-20 04:38:17 +07:00
"@coder/ide/src/fill/client": "<rootDir>/ide/src/fill/client",
Move and refactor fs tests
2019-02-20 03:21:04 +07:00
"@coder/(.*)/test": "<rootDir>/$1/test",
Fix install from VSIX for TAR and ZIP formats (#245) * Fix install from VSIX for TAR and ZIP formats * Parse TAR before ZIP, when installing from VSIX
2019-03-22 02:04:09 +07:00
"@coder/(.*)": "<rootDir>/$1/src",
"vs/(.*)": "<rootDir>/../lib/vscode/src/vs/$1",
Refactor evaluations (#285) * Replace evaluations with proxies and messages * Return proxies synchronously Otherwise events can be lost. * Ensure events cannot be missed * Refactor remaining fills * Use more up-to-date version of util For callbackify. * Wait for dispose to come back before removing This prevents issues with the "done" event not always being the last event fired. For example a socket might close and then end, but only if the caller called end. * Remove old node-pty tests * Fix emitting events twice on duplex streams * Preserve environment when spawning processes * Throw a better error if the proxy doesn't exist * Remove rimraf dependency from ide * Update net.Server.listening * Use exit event instead of killed Doesn't look like killed is even a thing. * Add response timeout to server * Fix trash * Require node-pty & spdlog after they get unpackaged This fixes an error when running in the binary. * Fix errors in down emitter preventing reconnecting * Fix disposing proxies when nothing listens to "error" event * Refactor event tests to use jest.fn() * Reject proxy call when disconnected Otherwise it'll wait for the timeout which is a waste of time since we already know the connection is dead. * Use nbin for binary packaging * Remove additional module requires * Attempt to remove require for local bootstrap-fork * Externalize fsevents
2019-03-27 01:01:25 +07:00
"vszip": "<rootDir>/../lib/vscode/src/vs/base/node/zip.ts",
"^node-pty": "node-pty-prebuilt"
not finished
2019-01-08 07:46:19 +07:00
},
"transform": {
"^.+\\.tsx?$": "ts-jest"
},
"testPathIgnorePatterns": [
"/node_modules/",
"/logger/"
],
"testRegex": ".*\\.test\\.tsx?"
}
Refactor evaluations (#285) * Replace evaluations with proxies and messages * Return proxies synchronously Otherwise events can be lost. * Ensure events cannot be missed * Refactor remaining fills * Use more up-to-date version of util For callbackify. * Wait for dispose to come back before removing This prevents issues with the "done" event not always being the last event fired. For example a socket might close and then end, but only if the caller called end. * Remove old node-pty tests * Fix emitting events twice on duplex streams * Preserve environment when spawning processes * Throw a better error if the proxy doesn't exist * Remove rimraf dependency from ide * Update net.Server.listening * Use exit event instead of killed Doesn't look like killed is even a thing. * Add response timeout to server * Fix trash * Require node-pty & spdlog after they get unpackaged This fixes an error when running in the binary. * Fix errors in down emitter preventing reconnecting * Fix disposing proxies when nothing listens to "error" event * Refactor event tests to use jest.fn() * Reject proxy call when disconnected Otherwise it'll wait for the timeout which is a waste of time since we already know the connection is dead. * Use nbin for binary packaging * Remove additional module requires * Attempt to remove require for local bootstrap-fork * Externalize fsevents
2019-03-27 01:01:25 +07:00
}
Reference in New Issue Copy Permalink