You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Dependencies for `/extension/css-language-features/`
7
+
- Dependencies for `/extension/css-language-features/server/`
8
+
- devDependencies such as `gulp`
9
+
- Open `/extensions/css-language-features/` as the workspace in VS Code
10
+
- Run the [`Launch Extension`](https://github.com/Microsoft/vscode/blob/master/extensions/css-language-features/.vscode/launch.json) debug target in the Debug View. This will:
11
+
- Launch the `preLaunchTask` task to compile the extension
12
+
- Launch a new VS Code instance with the `css-language-features` extension loaded
13
+
- You should see a notification saying the development version of `css-language-features` overwrites the bundled version of `css-language-features`
14
+
- Test the behavior of this extension by editing CSS/SCSS/Less files
15
+
- Run `Reload Window` command in the launched instance to reload the extension
16
+
17
+
### Contribute to vscode-css-languageservice
18
+
19
+
[Microsoft/vscode-css-languageservice](https://github.com/Microsoft/vscode-css-languageservice) contains the language smarts for CSS/SCSS/Less.
20
+
This extension wraps the css language service into a Language Server for VS Code.
21
+
If you want to fix CSS/SCSS/Less issues or make improvements, you should make changes at [Microsoft/vscode-css-languageservice](https://github.com/Microsoft/vscode-css-languageservice).
22
+
23
+
However, within this extension, you can run a development version of `vscode-css-languageservice` to debug code or test language features interactively:
24
+
25
+
#### Linking `vscode-css-languageservice` in `css-language-features/server/`
- Run `yarn link` in `vscode-css-languageservice`. This will compile and link `vscode-css-languageservice`
30
+
- In `css-language-features/server/`, run `npm link vscode-css-languageservice`
31
+
32
+
#### Testing the development version of `vscode-css-languageservice`
33
+
34
+
- Open both `vscode-css-languageservice` and this extension in a single workspace with [multi-root workspace](https://code.visualstudio.com/docs/editor/multi-root-workspaces) feature
35
+
- Run `yarn watch` at `css-languagefeatures/server/` to recompile this extension with the linked version of `vscode-css-languageservice`
36
+
- Make some changes in `vscode-css-languageservice`
37
+
- Now when you run `Launch Extension` debug target, the launched instance will use your development version of `vscode-css-languageservice`. You can interactively test the language features.
38
+
- You can also run the `Debug Extension and Language Server` debug target, which will launch the extension and attach the debugger to the language server. After successful attach, you should be able to hit breakpoints in both `vscode-css-languageservice` and `css-language-features/server/`
- Dependencies for `/extension/css-language-features/`
19
-
- Dependencies for `/extension/css-language-features/server/`
20
-
- devDependencies such as `gulp`
21
-
- Open `/extensions/css-language-features/` as the workspace in VS Code
22
-
- Run the [`Launch Extension`](https://github.com/Microsoft/vscode/blob/master/extensions/css-language-features/.vscode/launch.json) debug target in the Debug View. This will:
23
-
- Launch the `preLaunchTask` task to compile the extension
24
-
- Launch a new VS Code instance with the `css-language-features` extension loaded
25
-
- You should see a notification saying the development version of `css-language-features` overwrites the bundled version of `css-language-features`
26
-
- Test the behavior of this extension by editing CSS/SCSS/Less files
27
-
- Run `Reload Window` command in the launched instance to reload the extension
28
-
29
-
### Contribute to vscode-css-languageservice
30
-
31
-
[Microsoft/vscode-css-languageservice](https://github.com/Microsoft/vscode-css-languageservice) contains the language smarts for CSS/SCSS/Less.
32
-
This extension wraps the css language service into a Language Server for VS Code.
33
-
If you want to fix CSS/SCSS/Less issues or make improvements, you should make changes at [Microsoft/vscode-css-languageservice](https://github.com/Microsoft/vscode-css-languageservice).
34
-
35
-
However, within this extension, you can run a development version of `vscode-css-languageservice` to debug code or test language features interactively:
36
-
37
-
#### Linking `vscode-css-languageservice` in `css-language-features/server/`
- Run `yarn link` in `vscode-css-languageservice`. This will compile and link `vscode-css-languageservice`
42
-
- In `css-language-features/server/`, run `npm link vscode-css-languageservice`
43
-
44
-
#### Testing the development version of `vscode-css-languageservice`
45
-
46
-
- Open both `vscode-css-languageservice` and this extension in a single workspace with [multi-root workspace](https://code.visualstudio.com/docs/editor/multi-root-workspaces) feature
47
-
- Run `yarn watch` at `css-languagefeatures/server/` to recompile this extension with the linked version of `vscode-css-languageservice`
48
-
- Make some changes in `vscode-css-languageservice`
49
-
- Now when you run `Launch Extension` debug target, the launched instance will use your development version of `vscode-css-languageservice`. You can interactively test the language features.
50
-
- You can also run the `Debug Extension and Language Server` debug target, which will launch the extension and attach the debugger to the language server. After successful attach, you should be able to hit breakpoints in both `vscode-css-languageservice` and `css-language-features/server/`
Read the basics about extension authoring from [Extending Visual Studio Code](https://code.visualstudio.com/docs/extensions/overview)
4
+
5
+
- Read [Build and Run VS Code from Source](https://github.com/Microsoft/vscode/wiki/How-to-Contribute#build-and-run-from-source) to get a local dev set up running for VS Code
6
+
- Open the `extensions/emmet` folder in the vscode repo in VS Code
7
+
- Press F5 to start debugging
8
+
9
+
## Running tests
10
+
11
+
Tests for Emmet extension are run as integration tests as part of VS Code.
12
+
13
+
- Read [Build and Run VS Code from Source](https://github.com/Microsoft/vscode/wiki/How-to-Contribute#build-and-run-from-source) to get a local dev set up running for VS Code
14
+
- Run `./scripts/test-integration.sh` to run all the integrations tests that include the Emmet tests.
Copy file name to clipboardExpand all lines: extensions/emmet/README.md
-13Lines changed: 0 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,20 +6,7 @@
6
6
7
7
See [Emmet in Visual Studio Code](https://code.visualstudio.com/docs/editor/emmet)
8
8
9
-
## How to build and run from source?
10
9
11
-
Read the basics about extension authoring from [Extending Visual Studio Code](https://code.visualstudio.com/docs/extensions/overview)
12
-
13
-
- Read [Build and Run VS Code from Source](https://github.com/Microsoft/vscode/wiki/How-to-Contribute#build-and-run-from-source) to get a local dev set up running for VS Code
14
-
- Open the `extensions/emmet` folder in the vscode repo in VS Code
15
-
- Press F5 to start debugging
16
-
17
-
## Running tests
18
-
19
-
Tests for Emmet extension are run as integration tests as part of VS Code.
20
-
21
-
- Read [Build and Run VS Code from Source](https://github.com/Microsoft/vscode/wiki/How-to-Contribute#build-and-run-from-source) to get a local dev set up running for VS Code
22
-
- Run `./scripts/test-integration.sh` to run all the integrations tests that include the Emmet tests.
- Dependencies for `/extension/html-language-features/`
6
+
- Dependencies for `/extension/html-language-features/server/`
7
+
- devDependencies such as `gulp`
8
+
- Open `/extensions/html-language-features/` as the workspace in VS Code
9
+
- Run the [`Launch Extension`](https://github.com/Microsoft/vscode/blob/master/extensions/html-language-features/.vscode/launch.json) debug target in the Debug View. This will:
10
+
- Launch the `preLaunchTask` task to compile the extension
11
+
- Launch a new VS Code instance with the `html-language-features` extension loaded
12
+
- You should see a notification saying the development version of `html-language-features` overwrites the bundled version of `html-language-features`
13
+
- Test the behavior of this extension by editing html files
14
+
- Run `Reload Window` command in the launched instance to reload the extension
15
+
16
+
### Contribute to vscode-html-languageservice
17
+
18
+
[Microsoft/vscode-html-languageservice](https://github.com/Microsoft/vscode-html-languageservice) contains the language smarts for html.
19
+
This extension wraps the html language service into a Language Server for VS Code.
20
+
If you want to fix html issues or make improvements, you should make changes at [Microsoft/vscode-html-languageservice](https://github.com/Microsoft/vscode-html-languageservice).
21
+
22
+
However, within this extension, you can run a development version of `vscode-html-languageservice` to debug code or test language features interactively:
23
+
24
+
#### Linking `vscode-html-languageservice` in `html-language-features/server/`
- Run `yarn link` in `vscode-html-languageservice`. This will compile and link `vscode-html-languageservice`
29
+
- In `html-language-features/server/`, run `npm link vscode-html-languageservice`
30
+
31
+
#### Testing the development version of `vscode-html-languageservice`
32
+
33
+
- Open both `vscode-html-languageservice` and this extension in a single workspace with [multi-root workspace](https://code.visualstudio.com/docs/editor/multi-root-workspaces) feature
34
+
- Run `yarn watch` at `html-languagefeatures/server/` to recompile this extension with the linked version of `vscode-html-languageservice`
35
+
- Make some changes in `vscode-html-languageservice`
36
+
- Now when you run `Launch Extension` debug target, the launched instance will use your development version of `vscode-html-languageservice`. You can interactively test the language features.
37
+
- You can also run the `Debug Extension and Language Server` debug target, which will launch the extension and attach the debugger to the language server. After successful attach, you should be able to hit breakpoints in both `vscode-html-languageservice` and `html-language-features/server/`
- Dependencies for `/extension/html-language-features/`
20
-
- Dependencies for `/extension/html-language-features/server/`
21
-
- devDependencies such as `gulp`
22
-
- Open `/extensions/html-language-features/` as the workspace in VS Code
23
-
- Run the [`Launch Extension`](https://github.com/Microsoft/vscode/blob/master/extensions/html-language-features/.vscode/launch.json) debug target in the Debug View. This will:
24
-
- Launch the `preLaunchTask` task to compile the extension
25
-
- Launch a new VS Code instance with the `html-language-features` extension loaded
26
-
- You should see a notification saying the development version of `html-language-features` overwrites the bundled version of `html-language-features`
27
-
- Test the behavior of this extension by editing html files
28
-
- Run `Reload Window` command in the launched instance to reload the extension
29
-
30
-
### Contribute to vscode-html-languageservice
31
-
32
-
[Microsoft/vscode-html-languageservice](https://github.com/Microsoft/vscode-html-languageservice) contains the language smarts for html.
33
-
This extension wraps the html language service into a Language Server for VS Code.
34
-
If you want to fix html issues or make improvements, you should make changes at [Microsoft/vscode-html-languageservice](https://github.com/Microsoft/vscode-html-languageservice).
35
-
36
-
However, within this extension, you can run a development version of `vscode-html-languageservice` to debug code or test language features interactively:
37
-
38
-
#### Linking `vscode-html-languageservice` in `html-language-features/server/`
- Run `yarn link` in `vscode-html-languageservice`. This will compile and link `vscode-html-languageservice`
43
-
- In `html-language-features/server/`, run `npm link vscode-html-languageservice`
44
-
45
-
#### Testing the development version of `vscode-html-languageservice`
46
-
47
-
- Open both `vscode-html-languageservice` and this extension in a single workspace with [multi-root workspace](https://code.visualstudio.com/docs/editor/multi-root-workspaces) feature
48
-
- Run `yarn watch` at `html-languagefeatures/server/` to recompile this extension with the linked version of `vscode-html-languageservice`
49
-
- Make some changes in `vscode-html-languageservice`
50
-
- Now when you run `Launch Extension` debug target, the launched instance will use your development version of `vscode-html-languageservice`. You can interactively test the language features.
51
-
- You can also run the `Debug Extension and Language Server` debug target, which will launch the extension and attach the debugger to the language server. After successful attach, you should be able to hit breakpoints in both `vscode-html-languageservice` and `html-language-features/server/`
0 commit comments