#Tauri 2.0 beta Shell Sidecar `PluginInitialization("shell", "unknown field scope, expected open")`

9 messages · Page 1 of 1 (latest)

silent sleet
#

I updated to 2.0.0-beta and all works except sidecar
This part in config related to sidecar (shell plugin)

...
    "plugins": {
        "shell": {
            "scope": [
                {
                    "name": "binaries/api",
                    "sidecar": true
                }
            ]
        }
    }
...

Does anyone have an example of what changed since last time for shell plugin?

peak arrow
silent sleet
#

so in my case something like this would be in place in capabilities/base.json?

...
       {
            "identifier": "shell:allow-execute",
            "allow": [
                {
                    "name": "binaries/app"
                }
            ]
        },
...

Do I need to define it anywhere else? Like in tauri.config.json. There was previously "externalBin": ["binaries/api"], inside of bundle object and plugins => shell => scope (as in example above)

peak arrow
#

externalBin is still being used

#

just the scope was moved

silent sleet
#

ok, so capabilities are in place, I am not sure if I should be adding anything else since I can't find a single example of sidecar in v2 😄

Attached is error of cmd.execute() (code bellow) which happens after build when I add scope with just name, I am not sure what is it refering to, since I didn't define params.

    const cmd = Command.sidecar("binaries/api")
    console.log("Starting API")
    cmd.execute()
        .then((res) => {
            console.log("API Started", res)
        })
        .catch((err) => {
            console.error("API Error", err)
        })
peak arrow
#

i think sidecar: true is still a thing in base.json allow

silent sleet
#

that was it 😄 thanx a lot

#

will mark it as resolved