dac6f4b073
Removes unnecessary complexity |
||
---|---|---|
.. | ||
build | ||
public | ||
src | ||
.gitignore | ||
README.md | ||
package.json | ||
webpack.config.js |
README.md
Transformers.js - Sample browser extension
An example project to show how to run 🤗 Transformers in a browser extension. Although we only provide instructions for running in Chrome, it should be similar for other browsers.
Getting Started
-
Clone the repo and enter the project directory:
git clone https://github.com/xenova/transformers.js.git cd transformers.js/examples/extension/
-
Install the necessary dependencies:
npm install
-
Build the project:
npm run build
-
Add the extension to your browser. To do this, go to
chrome://extensions/
, enable developer mode (top right), and click "Load unpacked". Select thebuild
directory from the dialog which appears and click "Select Folder". -
That's it! You should now be able to open the extenion's popup and use the model in your browser!
Editing the template
We recommend running npm run dev
while editing the template as it will rebuild the project when changes are made.
All source code can be found in the ./src/
directory:
-
background.js
(service worker) - handles all the requests from the UI, does processing in the background, then returns the result. You will need to reload the extension (by visitingchrome://extensions/
and clicking the refresh button) after editing this file for changes to be visible in the extension. -
content.js
(content script) - contains the code which is injected into every page the user visits. You can use thesendMessage
api to make requests to the background script. Similarly, you will need to reload the extension after editing this file for changes to be visible in the extension. -
popup.html
,popup.css
,popup.js
(toolbar action) - contains the code for the popup which is visible to the user when they click the extension's icon from the extensions bar. For development, we recommend opening thepopup.html
file in its own tab by visitingchrome-extension://<ext_id>/popup.html
(remember to replace<ext_id>
with the extension's ID). You will need to refresh the page while you develop to see the changes you make.