[docs] Debug recipe for visual studio code updated (#1375) #1382
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
georgiy-abbasov
force-pushed
the
update-debug-recipes
branch
from
50b2ca3
to
ddecd23
Compare
georgiy-abbasov
changed the title
VasilyStrelyaev
requested changes
Apr 6, 2017
| @@ -44,12 +45,15 @@ You will need to add the following configuration to the `launch.json` file. | |||
| This configuration contains the following attributes: | |||
|
|
|||
| * `type` - specifies the type of the configuration. Set to `node` for a Node.js configuration. | |||
| * `protocol` - specifies Node.js [debugger wire protocol](https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_supported-nodelike-runtimes). | |||
There was a problem hiding this comment.
* `protocol` - specifies the Node.js [debugger wire protocol](https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_supported-nodelike-runtimes). Set to `inspector` to use the [Inspector protocol](https://chromedevtools.github.io/debugger-protocol-viewer/v8/). This protocol is available in Node.js v6.3 (or v6.9 for Windows) or newer. If you are using an older Node.js, do not specify the `protocol` option. In this instance, the `Legacy` protocol will be used.
| * `request` - specifies the request type. Set to `launch` since this configuration launches a program. | ||
| * `name` - specifies the name of the configuration. | ||
| * `program` - path to a JS file that will be executed. In this case, it is the TestCafe module. | ||
| * `args` - [command line arguments](../using-testcafe/command-line-interface.md) passed to the launched program. In this case, they specify the browser in which the tests should run and the test file. | ||
| * `cwd` - the current working directory. Set to the workspace root. | ||
|
|
||
| **Note**: Prior to Node.js v6.3 (or v6.9 for Windows), the debugger protocol had several issues and limitations. To ensure that the debugger works correctly, use newer Node.js versions that support the [Inspector debugging protocol](https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_supported-nodelike-runtimes). |
There was a problem hiding this comment.
removing this note
georgiy-abbasov
force-pushed
the
update-debug-recipes
branch
from
ddecd23
to
b55455d
Compare
|
\cc @DevExpress/testcafe-docs |
VasilyStrelyaev
approved these changes
Apr 7, 2017
inikulin
suggested changes
Apr 11, 2017
| @@ -44,6 +45,7 @@ You will need to add the following configuration to the `launch.json` file. | |||
| This configuration contains the following attributes: | |||
|
|
|||
| * `type` - specifies the type of the configuration. Set to `node` for a Node.js configuration. | |||
| * `protocol` - specifies the Node.js [debugger wire protocol](https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_supported-nodelike-runtimes). Set to `inspector` to use the [Inspector protocol](https://chromedevtools.github.io/debugger-protocol-viewer/v8/). This protocol is available in Node.js v6.3 (or v6.9 for Windows) or newer. If you are using an older Node.js, do not specify the `protocol` option. In this instance, the `Legacy` protocol will be used, which may cause issues with source maps while debugging test files. | |||
There was a problem hiding this comment.
Quite odd general phrasing. It sound like issues with source maps while debugging test files is some kind of feature and to enable it you need to avoid specifying protocol.
There was a problem hiding this comment.
* `protocol` - specifies the Node.js
[debugger wire protocol](https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_supported-nodelike-runtimes).
Set to `inspector` to use the [Inspector protocol](https://chromedevtools.github.io/debugger-protocol-viewer/v8/).
This protocol is available in Node.js v6.3 (or v6.9 for Windows) or newer.
Older Node.js versions do not support the `protocol` option.
They use the `Legacy` protocol that has issues with source maps.
|
FPR |
inikulin
suggested changes
Apr 11, 2017
| @@ -44,6 +45,7 @@ You will need to add the following configuration to the `launch.json` file. | |||
| This configuration contains the following attributes: | |||
|
|
|||
| * `type` - specifies the type of the configuration. Set to `node` for a Node.js configuration. | |||
| * `protocol` - specifies the Node.js [debugger wire protocol](https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_supported-nodelike-runtimes). Set to `inspector` to use the [Inspector protocol](https://chromedevtools.github.io/debugger-protocol-viewer/v8/). This protocol is available in Node.js v6.3 (or v6.9 for Windows) or newer. Older Node.js versions do not support the `protocol` option. They use the `Legacy` protocol that has issues with source maps. | |||
There was a problem hiding this comment.
specifies the Node.js [debugger wire protocol](https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_supported-nodelike-runtimes). Note that inspector protocol is supported in Node.js v6.3 (or v6.9 for Windows) or later. For early versions omit this property. In that case legacy debugger protocol will be used. Legacy protocol is well known for it's issues with source map support, therefore newer versions of Node.js are recommended.
\cc @VasilyStrelyaev
georgiy-abbasov
force-pushed
the
update-debug-recipes
branch
from
2e285fb
to
15d7155
Compare
|
FPR |
kirovboris
approved these changes
Apr 11, 2017
kirovboris
pushed a commit
to kirovboris/testcafe-phoenix
that referenced
this pull request
Dec 18, 2019
…evExpress#1382) * [docs] Debug recipe for visual studio code updated (DevExpress#1375) * Fix remark
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@DevExpress/testcafe-docs