Simple & crude chrome extension to get the 'underlining' real video url that works with yt-dl.
If you want to try this:
- clone the repo
- install dependencies
- run the build script,
npm run build
- go to chrome extension page, check developer mode, click
load unpacked
& choose the generatedbuild
folder
Bootstrapped with Chrome Extension Webpack Boilerplate
Webpack docs Chrome Extension docs._
All your extension's development code must be placed in src
folder, including the extension manifest.
The boilerplate is already prepared to have a popup, a options page and a background page. You can easily customize this.
To make your workflow much more efficient this boilerplate uses the webpack server to development (started with yarn run server
) with auto reload feature that reloads the browser automatically every time that you save some file on your editor.
You can run the dev mode on other port if you want. Just specify the env var port
like this:
$ PORT=6002 yarn run start
Although this boilerplate uses the webpack dev server, it's also prepared to write all your bundles files on the disk at every code change, so you can point, on your extension manifest, to your bundles that you want to use as content scripts, but you need to exclude these entry points from hot reloading (why?). To do so you need to expose which entry points are content scripts on the webpack.config.js
using the chromeExtensionBoilerplate -> notHotReload
config. Look the example below.
Let's say that you want use the myContentScript
entry point as content script, so on your webpack.config.js
you will configure the entry point and exclude it from hot reloading, like this:
{
…
entry: {
myContentScript: "./src/js/myContentScript.js"
},
chromeExtensionBoilerplate: {
notHotReload: ["myContentScript"]
}
…
}
and on your src/manifest.json
:
{
"content_scripts": [
{
"matches": ["https://www.google.com/*"],
"js": ["myContentScript.bundle.js"]
}
]
}
After the development of your extension run the command
$ NODE_ENV=production yarn run build
Now, the content of build
folder will be the extension ready to be submitted to the Chrome Web Store. Just take a look at the official guide to more infos about publishing.
If you are developing an extension that talks with some API you probably are using different keys for testing and production. Is a good practice you not commit your secret keys and expose to anyone that have access to the repository.
To this task this boilerplate import the file ./secrets.<THE-NODE_ENV>.js
on your modules through the module named as secrets
, so you can do things like this:
./secrets.development.js
export default { key: "123" };
./src/popup.js
import secrets from "secrets";
ApiCall({ key: secrets.key });
👉 The files with name secrets.*.js
already are ignored on the repository.
💡 If you want use React.js with this boilerplate, check the react branch.