Install
Two ways in: load the folder as an unpacked extension (best for development), or install the packaged zip from a release.
Load unpacked
Step 1 — clone or download the repository and note the folder that contains
manifest.json.
git clone https://github.com/pavnxet/freerammer.git freerammer
cd freerammer
Step 2 — open chrome://extensions and switch on Developer mode
in the top-right corner.
Step 3 — click Load unpacked and select the repository folder.
Step 4 — pin the extension from the puzzle-piece menu. The popup opens on the toolbar icon.
_metadata/. That folder is a
Chrome artifact written whenever an unpacked extension loads. It is git-ignored — do not commit it, and do
not be surprised when it reappears.Packaged release
Every tagged release publishes a zip built from the repository by the release workflow.
- Open the releases page.
- Download
freerammer-v<version>.zipfor the version you want. - Unzip it, then load the unzipped folder the same way as above.
Build it yourself
npm run verify # VERSION, manifest.json and package.json must agree
npm run package # writes dist/freerammer-v<version>.zip
First run
On install the extension writes its defaults, marks the profile as fully unlocked, and starts the suspension alarm. A few things worth knowing:
- Defaults are conservative: ad and tracker blocking is at level 3, video ads and cookie banners are on, and the heavier features (image blocking, font substitution, autoplay) start off.
- The badge shows cumulative RAM saved since install.
- Nothing leaves your browser. There is no sign-in step and no welcome page.
Updating
For an unpacked install, pull the new code and hit Reload on the extension card. For a packaged install, unzip the newer release over the old folder and reload.