Test for #6915:

• Windows - @roblourens

  OS X - @ramya-rao-a

  Linux - @Tyriar
  To pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.

Complexity 3

When debugging transpiled code (e.g. TypeScript) and the build process generates the JavaScript code into a specific directory, it is necessary to help the node debugger finding this generated code. In previous version of VS Code this was done by specifying the root directory of the generated code via the outDir attribute.

In this release it is now possible to use multiple glob patterns for including and excluding files from the set of generated JavaScript files. For this a new array typed attribute outFiles has been introduced. The old outDir is still supported, but we plan to deprecated this in the future.

The following example shows how to configure source maps if the generated code lives in an "out" and "node_modules" directory and you want to exclude the generated test code:

  "sourceMaps": true,
  "outFiles": [
    "${workspaceRoot}/{out,node_modules}/**/*.js",
    "!${workspaceRoot}/out/tests/**/*.js"
  ]

Verify this feature with an 'interesting' source map setup as follows:

• launch a debug session
• as long as outFiles hasn't been configured, setting a breakpoint in source should result in an unverified (grey) breakpoint because node-debug cannot find the corresponding generated code (which should have a 'sourceMappingURL' that points to the source via a source map).
• configure the outFiles attribute and restart debug session
• now the breakpoint should verify (and should be hit).