Skip to content

Commit

Permalink
Update WEB-EXTENSIONS-HOWTO.md
Browse files Browse the repository at this point in the history
  • Loading branch information
Apollon77 authored Oct 1, 2024
1 parent 67dc557 commit 95b203e
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions WEB-EXTENSIONS-HOWTO.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,8 @@ First, it must have a `common.webExtension` flag in `io-package.json` file that
Second, `native.webInstance` flag in `io-package.json` has to point to the instance name of the web-adapter for which the extension should be loaded.
Or simply load it for all instances via `"webInstance": "*"`.

Third, make sure `common.enabled` is set to true in `io-package.json`: `"enabled": true`.
If you're working with **dev-server** please note: dev-server does **not set the instance to enabled**, you have to do this manually: Navigate to `system.adapter.<ADAPTER_NAME>.0`, use `edit object` to set `"enabled": true` within object data. If not set correctly, the web extension will not be activated by web adapter.
Third, make sure `common.enabled` of the respective web-extension adapter is set to true in `io-package.json`: `"enabled": true`.
If you're working with **dev-server** please note: dev-server does **not set the instance to enabled** when using "dev-server watch", you have to do this manually: Navigate to `system.adapter.<ADAPTER_NAME>.0`, use `edit object` to set `"enabled": true` within object data. If not set correctly, the web extension will not be activated by web adapter.

Fourth, the file `lib/web.js` (or whatever) must exist, and it must export a class.
```
Expand Down

0 comments on commit 95b203e

Please sign in to comment.