"chrome-extension://*", "file:///*" in permissions "chromium-args": "-load-extension=Users/usernamehere/Desktop/gbkeegbaiigmenfmjfclcdgdpimamgkj -enable-logging -v=1", In a NW.js app package - should it be in the appdata profile as for Chrome? Begs the question of where the location of the extension folder should be I have noticed that the chromium-args path needs to be a full path, relative will not work. Run after a delay all the files in the extension folder were deleted except for the manifest.json so NW.js is trying to do something with the extension. The extension was retrieved from the Chrome appdata folders (Library/Application Support/Google/Chrome/Default/Extensions) in unpacked form.Īt one point I tried to place the extension into the app profile manually ( Library/Application Support/Office/Default/Extensions) and when the app (Office) was I used similar techniques for the Office extn. I tried the react-tools extn and it works fine so I guess this is covered by chrome.tabs I suspect that NW.js is not enabled for this type of extn since the docs list only ntentSettings, chrome.tabs and chrome.proxy as supported. This works quite well in Chrome and wanting to use it in a wee project. Trying to use the Google Extension - Office Editing for Docs, Sheets & Slides.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |