The host manifest file describes the relationship
between an application a browser extensions.
My Host Manifest.json
{
"allowed_origins" : [ "<Extension Url>" ] ,
"description" : "" ,
"type" : "<Communication Type>" ,
"path" : "<App Path>" ,
"name" : "<App Id>"
}Unique identifier that, in extensions,
is used to connect to one another.
For windows users, the appId is the name of the
registry key that points towards this host manifest.
-
Cannot have multiple
.in a row -
Cannot start / end with
. -
a - Z0 - 9._
-
microsoft.graph_editor.updater -
mike00341.important_project -
cakemakers.editor
The communication interface used.
Currently only has one valid type.
-
stdioIndicates communication with
stdin/stdout
A simple description of the native app.
System path to the application that will be used
when in communication with the extension.
Relative paths start from this host manifest.
| OS | Windows | Linux | OSX |
|---|---|---|---|
| 🟢 | 🔴 | 🔴 |
-
/Editor.jsWith the manifest located in
the same folder asEditor.js
-
C:/cakeMaker/Editor.js
The current working directory will be set
to the folder of the binary as it is started.
C:\myApplication\App.exe
⤷ C:\myApplication\
A list of extensions that are allowed
to communicate with the native app.
chrome-extension://<Extension Id>/
You can find your extension's
Id at chrome://extensions/
chrome-extension://bgfcmdaggdanlogtkdephpqcojfbobmm/