How to use jQuery in chrome extension

Question

I am writing a chrome extension  And I want to use jQuery in my extension  I am not using any background page  just a background script   Here are my files    manifest json         manifest version   2        name    Extension name        description    This extension does something         version    0 1         permissions              activeTab               browser action              default icon    images icon 128 png               background              scripts     background js             persistent   false              icons              16    images icon 16 png            48    images icon 48 png            128    images icon 128 png            My background js file just runs another file named work js     Respond to the click on extension Icon chrome browserAction onClicked addListener function  tab        chrome tabs executeScript           file   work js                The main logic of my extension is inside work js  The contents of which I don t think matters here for this question   What I want to ask is how can I use jQuery in my extension  Since I am not using any background page  I can t just add jQuery to it  So how can I add and use jQuery into my extension    I tried running jQuery along with my work js from background js file      Respond to the click on extension Icon chrome browserAction onClicked addListener function  tab        chrome tabs executeScript           file   thirdParty jquery-2 0 3 js              chrome tabs executeScript           file   work js                And it works fine  but I am having the concern whether the scripts added to be executed in this manner are being executed asynchronously  If yes then it can happen that work js runs even before jQuery  or other libraries which I may add in future    And I would also like to know what s the correct and best way to use third party libraries  in my chrome extension

User · Answer

You have to add your jquery script to your chrome-extension project and to the background section of your manifest.json like this :

  "background":
    {
        "scripts": ["thirdParty/jquery-2.0.3.js", "background.js"]
    }

If you need jquery in a content_scripts, you have to add it in the manifest too:

"content_scripts": 
    [
        {
            "matches":["http://website*"],
            "js":["thirdParty/jquery.1.10.2.min.js", "script.js"],
            "css": ["css/style.css"],
            "run_at": "document_end"
        }
    ]

This is what I did.

Also, if I recall correctly, the background scripts are executed in a background window that you can open via chrome://extensions.

User · Answer

In my case got a working solution through Cross-document Messaging  XDM  and Executing Chrome extension onclick instead of page load   manifest json       name    JQuery Light      version    1      manifest version   2      browser action          default icon    icon png           content scripts                  matches              https     google com                    js              jquery-3 3 1 min js            myscript js                         background          scripts            background js                 background js  chrome browserAction onClicked addListener function  tab      chrome tabs query  active  true  currentWindow  true   function  tabs        var activeTab   tabs 0       chrome tabs sendMessage activeTab id    message    clicked browser action                 myscript js  chrome runtime onMessage addListener      function  request  sender  sendResponse            if  request message      clicked browser action             console log  Hello world

User · Answer

And it works fine  but I am having the concern whether the scripts added to be executed in this manner are being executed asynchronously  If yes then it can happen that work js runs even before jQuery  or other libraries which I may add in future     That shouldn t really be a concern  you queue up scripts to be executed in a certain JS context  and that context can t have a race condition as it s single-threaded   However  the proper way to eliminate this concern is to chain the calls   chrome browserAction onClicked addListener function  tab        chrome tabs executeScript           file   thirdParty jquery-2 0 3 js         function                Guaranteed to execute only after the previous script returns         chrome tabs executeScript               file   work js                            Or  generalized   function injectScripts scripts  callback      if scripts length        var script   scripts shift        chrome tabs executeScript  file  script   function           if chrome runtime lastError  amp  amp  typeof callback      function             callback false      Injection failed               injectScripts scripts  callback               else       if typeof callback      function           callback true                injectScripts   thirdParty jquery-2 0 3 js    work js    doSomethingElse     Or  promisified  and brought more in line with the proper signature    function injectScript tabId  injectDetails      return new Promise  resolve  reject    gt        chrome tabs executeScript tabId  injectDetails   data    gt          if  chrome runtime lastError            reject chrome runtime lastError message           else           resolve data                            injectScript null   file   thirdParty jquery-2 0 3 js    then         gt  injectScript null   file   work js      then         gt  doSomethingElse   catch     error    gt  console error error       Or  why the heck not  async await-ed for even clearer syntax   function injectScript tabId  injectDetails      return new Promise  resolve  reject    gt        chrome tabs executeScript tabId  injectDetails   data    gt          if  chrome runtime lastError            reject chrome runtime lastError message           else           resolve data                            try     await injectScript null   file   thirdParty jquery-2 0 3 js       await injectScript null   file   work js       doSomethingElse      catch  err      console error err       Note  in Firefox you can just use browser tabs executeScript as it will return a Promise

User · Answer

Its very easy just do the following  add the following line in your manifest json  quot content security policy quot    quot script-src  self  https   ajax googleapis com  object-src  self  quot    Now you are free to load jQuery directly from url    lt script src  quot https   ajax googleapis com ajax libs jquery 2 2 2 jquery min js quot  gt  lt  script gt   Source  google doc

User · Answer

Apart from the solutions already mentioned  you can also download jquery min js locally and then use it -   For downloading -   wget  https   ajax googleapis com ajax libs jquery 3 1 0 jquery min js    manifest json -    content scripts               js      path to jquery min js                  in html -    lt script src   path to jquery min js  gt  lt  script gt    Reference - https   developer chrome com extensions contentSecurityPolicy

[javascript] How to use jQuery in chrome extension?

Examples related to javascript

Examples related to jquery

Examples related to google-chrome

Examples related to asynchronous

Examples related to google-chrome-extension