I cannot install the plugin

[vkhobor]

I searched in settings/plugin tab for insomnia-plugin-batch-requests, and the install process failed with:

Error: Error invoking remote method 'installPlugin': Error: Yarn error {"type":"warning","data":"package.json: No license field"}

    at IpcRenderer.invoke (node:electron/js2c/renderer_init:2:6995)
    at async onSubmit (file:///C:/Users/********/AppData/Local/insomnia/app-10.0.0/resources/app.asar/mainWindow-CnaQkWW6.js:1444:66352)

I tried installing from the plugin website, but it still failed. Now with empty stacktrace.

My instomnia version is v10.0.0, and I am on Windows.

Thanks.

[jreyesr]

Hello @vkhobor! Sorry to hear you're having trouble with the plugin, that seems really weird.

I've just installed Insomnia v10 on a Windows VM, and I've had no trouble installing the plugin. Besides, the error message seems to be a red herring, because the plugin does have a license (MIT), and it's recognized by NPM, so it should all be OK. I've found Kong/insomnia#4041, which is a fairly old (and theoretically closed) issue on Insomnia itself, which seems to match your issue. The person who reported it had trouble installing any plugin, as they all failed with the "no license found" error. Could you perhaps try to install another plugin? If you don't have any, insomnia-plugin-global-headers is the most installed Insomnia plugin (not that I use it, it's just the most popular one). Could you report if that plugin also causes the same error?

If other plugins cause the same error, could you check if, somewhere up the folder structure, there's a package.json file? In other words, Insomnia installs its plugins on C:\Users\Username\AppData\Roaming\Insomnia\plugins. Could you check the folders C:\Users\Username\AppData\Roaming\Insomnia, C:\Users\Username\AppData\Roaming, C:\Users\Username\AppData, C:\Users\Username, C:\Users and C:\, and see if any of them contain a file called package.json? Especially C:\Users\Username and C:\, the others aren't as likely to contain random files.

It's been reported that, if any if those folders contain a file package.json (e.g. you ran npm install <package> while in C:\Users\Username), it may cause problems. If you find it, and you don't need it (in the issue above that file had been created by mistake), try deleting it and then installing the plugin, it may be solved.