vue-cli-plugin-browser-extension | Browser extension development plugin

I'm trying to figure out what is the way to use hierarchical dependencies in node.

I'm building a VueJs chrome extension using Vue CLI and vue-cli-plugin-browser-extension (https://www.npmjs.com/package/vue-cli-plugin-browser-extension). In the background file I need to use two dependencies:

1. jquery
2. table-to-json (https://www.npmjs.com/package/table-to-json)

table-to-json needs jquery in order to work

I installed the two dependency using node install and require the dependencies in the background fild. But when I try to run the background script I get this error:

background.js:37 Uncaught ReferenceError: jQuery is not defined at Object.f370 (background.js:37) at n (background.js:1) at Object.fe77 (background.js:37) at n (background.js:1) at Object.1 (background.js:1) at n (background.js:1) at background.js:1 at background.js:1 f370 @ background.js:37 n @ background.js:1 fe77 @ background.js:37 n @ background.js:1 1 @ background.js:1 n @ background.js:1 (anonymous) @ background.js:1 (anonymous) @ background.js:1 DevTools failed to load SourceMap: Could not load content for chrome-extension://ljejdkiepkafbpnbacemjjcleckglnjl/js/background.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

table-to-json is not able to see jquery. What am I missing?

This is my background file, package.json and vue.config.js:

backgroung.js

I'm trying to implement a JSON viewer chrome extension. I already have the Viewer implemented with Vue (http://treedoc.org). Now the problem is how can I can inject the Vue page with Chrome extension content script.

I found this post is very helpful to inject normal javascript file in the extension. But this is with a known javascript file name.

I found this post and this vue-cli-plugin-browser-extension is helpful to use Vue for extension options page and override page, etc, as the entry point for them are HTML files. but the content script entry point is a javascript, to inject a javascript file in the content script, you need to know the exact file name. With the plugin and Webpack, the generated javascript files are appended with hash such as "override.0e5e7d0a.js" which is not known upfront.