In this case, they specify the browser in which the tests should run and the relative path to the test file.

args - command line arguments passed to the launched program.

In this case, this file is the TestCafe module.

program - path to the executed JS file.

name - specifies the configuration name.

Set to launch since this configuration launches a program. The legacy protocol has issues with source map support, therefore newer versions of Node.js are recommended. In that case, Node.js uses a legacy debugger protocol. Note that the inspector protocol is supported in Node.js v6.3 (or v6.9 for Windows) or later.

protocol - specifies the Node.js debugger wire protocol .

type - specifies the configuration type.

This configuration contains the following attributes: It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.Before you debug in Visual Studio Code, ensure that your root test directory contains a package.json file that includes testcafe in the devDependencies section.

Please remember to 'Mark as Answer' the responses that resolved your issue. By default it adds NodeJS debugging configuration, to add browser's debugger, press 'Add Configuration.' button in the left bottom corner of launch.json editor and choose 'Effectful: Browser'. #QuickStart: Debug JavaScript using the console įor your case, if you load those script programmtically (and execute fine at runtime), you can consider change the script to be statically referenced at development time so that you can use VS IDE to debug them as other standard Windows For this open Debugger view (Ctrl (Command)-Shift-D) and press create a launch.json file link, and choose 'Debug with EffectfulJS'.

Package and submit for store certification review.Īnd for script debugging, suppose all statically referenced script can be debugged and step through via VS IDE ( see following reference): And normally, store app expect developer to put all script code at dev time together with the app's other page assets (like htm file, images ,etc.) so that they can be packaged into the deployment And dynamic script execution is somewhat restricted in windows store app's code and it provides specificįunction for us to execute some dynamic script code at runtime. Many additional restrictions which make windows store app's javascript development different from pure HTML + javascript based web page development. Are you developing Windows Store app via javascript? If so, how do you load the dynamic script in your store app's code (via jquery)? For Windows Store app with javascript, although it provides web browser like script + html execution mode, there are

Visual studio code js debugger