Skip to content

Commit 1289b66

Browse files
committed
Updated README for July 2022
1 parent d87b05f commit 1289b66

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

README.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,10 @@ The aim of this repository is to help setting up Visual Studio Code for developm
55
Visual Studio Code comes with Electron support and Typescript support out of the box, but bringing the two together requires some advanced knowledge of the available configuration options. The repository contains a README with step by step instructions and an example project to demonstrate how Visual Studio Code, Node, Electron and Typescript must be configured to work together.
66

77
The latest example project has been created and tested on Linux with
8-
- Node v18.3.0
9-
- Electron v19.0.4
10-
- Typescript v4.7.3
11-
- Visual Studio Code v1.68.0
8+
- Node v18.6.0
9+
- Electron v19.0.8
10+
- Typescript v4.7.4
11+
- Visual Studio Code v1.69.1
1212

1313
## Install application
1414
```sh
@@ -48,14 +48,14 @@ npm start
4848
Electron has two kinds of processes: a main process and renderer processes (one for each tab). They need different launch configurations, which are shown below. The code snippets are taken from the [launch configuration](.vscode/launch.json).
4949

5050
### Main process
51-
The main process can be debugged with the pwa-node debugger, that ships with Visual Studio Code.
51+
The main process can be debugged with the node debugger, that ships with Visual Studio Code.
5252

5353
The launch configuration looks like this:
5454

5555
```jsonc
5656
{
5757
"name": "Electron: Main",
58-
"type": "pwa-node", //use the node debugger that comes with VS Code
58+
"type": "node", //use the node debugger that comes with VS Code
5959
"request": "launch",
6060
"cwd": "${workspaceFolder}",
6161
"runtimeExecutable": "${workspaceFolder}/node_modules/.bin/electron",
@@ -77,12 +77,12 @@ In the `sourceMaps` and `resolveSourceMapLocations` sections, we enable the crea
7777
In the `runtimeArgs` section, we open a port for the renderer process. There is a counterpart defined in the renderer process configuration as shown below.
7878

7979
### Renderer process
80-
A renderer process can be debugged with the pwa-chrome debugger, that ships with Visual Studio Code.
80+
A renderer process can be debugged with the chrome debugger, that ships with Visual Studio Code.
8181

8282
```jsonc
8383
{
8484
"name": "Electron: Renderer",
85-
"type": "pwa-chrome", //use the Chrome debugger that comes with VS Code
85+
"type": "chrome", //use the Chrome debugger that comes with VS Code
8686
"request": "attach",
8787
"port": 9223, //use debug port opened in Electron: Main configuration
8888
"webRoot": "${workspaceFolder}",

0 commit comments

Comments
 (0)