Cookie Muncher

Chrome extension (Manifest V3) that automates cookie consent banners based on your choice: reject all, necessary only, or accept all.

Privacy policy (public)

After you enable GitHub Pages (see below), your policy will be available at:

https://jvsperling.github.io/cookie-muncher/privacy-policy.html

Optional: replace your-email@example.com in docs/privacy-policy.html if you publish a contact email.

Enable GitHub Pages

1. Push this repo to GitHub (see Create the GitHub repo).
2. On GitHub: Settings → Pages.
3. Build and deployment: Source = Deploy from a branch.
4. Branch = main, folder = /docs → Save.

Development

• Load unpacked: chrome://extensions → Developer mode → Load unpacked → select this folder (without node_modules in the path; you can load the repo root if dependencies are only for build scripts).
• Icons: npm install then npm run generate-icons (requires source PNG in frames/).
• Store marketing images: npm run store:images -- /path/to/source.png

Store submission ZIP

Package only extension files (no node_modules, no dev-only folders). Example:

zip -r ../CookieMuncher-store.zip . \
  -x "node_modules/*" -x "scripts/*" -x "source-mascot-frames/*" \
  -x ".git/*" -x "*.zip" -x "package.json" -x "package-lock.json" \
  -x "chrome-store-assets/*" -x "frames/muncher-frame-*" -x "icons/monster.svg"

Adjust excludes to match what you ship; keep everything referenced in manifest.json.

Create the GitHub repo

Option A — GitHub website
Create a new public repository named cookie-muncher, then:

cd cookie-muncher
git remote add origin https://github.com/jvsperling/cookie-muncher.git
git branch -M main
git push -u origin main

Option B — GitHub CLI (gh auth login first):

cd cookie-muncher
gh repo create cookie-muncher --public --source=. --remote=origin --push

License

Add a LICENSE file if you want to specify terms for the source code.