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
Copy file name to clipboardExpand all lines: README.md
+14-6Lines changed: 14 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -88,7 +88,7 @@ For VSCode install the extension: https://marketplace.visualstudio.com/items?ite
88
88
89
89
Elixir:
90
90
91
-
- 1.12.3 minimum
91
+
- 1.12 minimum
92
92
93
93
Erlang:
94
94
@@ -108,7 +108,7 @@ Currently there is a limit of 100 breakpoints.
108
108
109
109
In order to debug modules in `.exs` files (such as tests), they must be specified under `requireFiles` in your launch configuration so they can be loaded and interpreted prior to running the task. For example, the default launch configuration for "mix test" in the VS Code plugin looks like this:
110
110
111
-
```
111
+
```json
112
112
{
113
113
"type": "mix_task",
114
114
"name": "mix test",
@@ -128,7 +128,7 @@ In order to debug modules in `.exs` files (such as tests), they must be specifie
128
128
129
129
In order to debug a single test or a single test file it is currently necessary to modify `taskArgs` and make sure no other tests are required in `requireFiles`.
130
130
131
-
```
131
+
```json
132
132
{
133
133
"type": "mix_task",
134
134
"name": "mix test",
@@ -148,7 +148,7 @@ In order to debug a single test or a single test file it is currently necessary
148
148
149
149
Use the following launch config to debug phoenix apps
150
150
151
-
```
151
+
```json
152
152
{
153
153
"type": "mix_task",
154
154
"name": "phx.server",
@@ -164,7 +164,7 @@ Please make sure that `startApps` is not set to `true` as it prevents phoenix fr
164
164
165
165
Please note that due to `:int` limitation NIF modules cannot be interpreted and need to be excluded via `excludeModules` option. This option can be also used to disable interpreting for some modules when it is not desirable e.g. when performance is not satisfactory.
Run `mix compile`, then `mix elixir_ls.release -o <release_dir>`. This builds the language server and debugger as a set of `.ez` archives and creates `.sh` and `.bat` scripts to launch them.
294
+
In order to build a release use the following commands.
This builds the language server and debugger as a set of `.ez` archives and creates `.sh` and `.bat` scripts to launch them.
295
303
296
304
If you're packaging these archives in an IDE plugin, make sure to build using the minimum supported OTP version for the best backwards-compatibility. Alternatively, you can use a [precompiled release](https://github.com/elixir-lsp/elixir-ls/releases).
0 commit comments