omnisharp-vscode/.vscodeignore

16 строки
188 B
Plaintext
Исходник Обычный вид История

Clean up npm scripts and start running tests Since the repo started, we've had a single NPM script that ran on postinstall. All this did was run the VS Code install script and then launch tsc. Now, postinstall just runs the VS Code install script. The idea here is that install should really just lay down dependencies, not compile code. Compilation is split off into a separate script. Here are the new npm scripts: * `postinstall`: As described above, this now just runs the VS Code install script after `npm install`. * `compile`: Runs the VS Code compile script to transpile TypeScript to JavaScript. Run this with `npm run compile`. * `watch`: Runs the VS Code compile script with the '-watch' flag to transpile TypeScript to JavaScript, and then watch for file changes and incrementally compile. Run this with `npm run watch`. * `test`: Runs the tests with Mocha. Note: This will only run tests that are already transpiled to JavaScript. Run with `npm test`. * Unit tests can be written in the 'test' folder. See 'test/sanity.tests.ts' for an example. * The launch.json has been updated to allow debugging of unit tests with the "Launch Tests" configuration. * The "test" task is now configured so that you can use the "Tasks: Run Test Task" command in VS Code. * Whitespace is a bit out of control. I've made an executable decision that the repo should have spaces with an indent size of 4. This is now added to the settings.json. * The 'out' folder is now excluded in settings.json so you won't see it show up in your directory tree. * The 'node_modules' folder is now excluded from search. This has been bothering me for awhile.
2016-08-27 19:11:31 +03:00
.vscode/**
typings/**
out/test/**
test/**
src/**
**/*.map
Clean up npm scripts and start running tests Since the repo started, we've had a single NPM script that ran on postinstall. All this did was run the VS Code install script and then launch tsc. Now, postinstall just runs the VS Code install script. The idea here is that install should really just lay down dependencies, not compile code. Compilation is split off into a separate script. Here are the new npm scripts: * `postinstall`: As described above, this now just runs the VS Code install script after `npm install`. * `compile`: Runs the VS Code compile script to transpile TypeScript to JavaScript. Run this with `npm run compile`. * `watch`: Runs the VS Code compile script with the '-watch' flag to transpile TypeScript to JavaScript, and then watch for file changes and incrementally compile. Run this with `npm run watch`. * `test`: Runs the tests with Mocha. Note: This will only run tests that are already transpiled to JavaScript. Run with `npm test`. * Unit tests can be written in the 'test' folder. See 'test/sanity.tests.ts' for an example. * The launch.json has been updated to allow debugging of unit tests with the "Launch Tests" configuration. * The "test" task is now configured so that you can use the "Tasks: Run Test Task" command in VS Code. * Whitespace is a bit out of control. I've made an executable decision that the repo should have spaces with an indent size of 4. This is now added to the settings.json. * The 'out' folder is now excluded in settings.json so you won't see it show up in your directory tree. * The 'node_modules' folder is now excluded from search. This has been bothering me for awhile.
2016-08-27 19:11:31 +03:00
.gitignore
.travis.yml
tsconfig.json
**/.nyc_output/**
**/coverage/**
+RuntimeLicenses/dependencies/*
coreclr-debug/install.log