Matt Bierner 2a1d11ed06 Disable open trigger file in configFileEvent ...

Workaround for #28593

**Bug**
TypeScript Server is hanging onto a file in `node_modules/.staging`, causing npm installs to fail. I believe the root cause is that 0d5c9f4 changed vscode logic to always open the `triggerFile` in config diagnostic events.  In this case, TS sends us a trigger file from `.staging` which we then tell the TS Server to open

**Fix**
Disable checking the trigger file

2017-07-05 15:06:48 -07:00

..

build

Add .mjs to known JavaScript file extensions (#25747)

2017-05-04 16:21:08 -07:00

schemas

…

snippets

Remove class snippet comment (#23209)

2017-04-03 16:57:50 -07:00

src

Disable open trigger file in configFileEvent

2017-07-05 15:06:48 -07:00

syntaxes

Update js/ts grammar

2017-06-20 13:51:31 -07:00

test

Reset JavaScript expression coloring in template expressions (#29966)

2017-06-30 16:11:48 -07:00

.vscodeignore

use vsce to determine what to package when bundling extensions

2017-06-21 16:17:21 +02:00

language-configuration.json

Fixes #13295: Remove brackets with problems

2016-10-27 21:40:46 +02:00

npm-shrinkwrap.json

update dependency on vscode-extension-telemetry

2017-06-30 09:57:37 -07:00

OSSREADME.json

…

package.json

update dependency on vscode-extension-telemetry

2017-06-30 09:57:37 -07:00

package.nls.json

Add insertSpaceAfterTypeAssertion formatting option

2017-06-28 05:06:53 -05:00

tsconfig.json

use alwaysStrict in TS extension

2017-05-24 15:03:50 -07:00