Open a separate Chrome profile
Use a browser profile you control for testing. Sign in to the GST Portal directly in that profile.
Pre-1.0 beta
Use a browser profile you control for testing. Sign in to the GST Portal directly in that profile.
The Chrome Web Store listing has version 0.5.1 of the beta. No release tag matches that package: tag v0.5.1 carries the same version number but an older manifest summary ("Alpha") and predates the Store build, which was made from later source that is not yet recorded. Building tag v0.5.1 lets you audit that tagged release, not the Store package. Enable Developer mode at chrome://extensions, choose Load unpacked, and select .output/chrome-mv3 from your local build.
Navigate to the supported filed GSTR‑3B or GSTR‑1, or auto-drafted GSTR‑2B, download area for an account and period you are authorised to access.
Open Pack, choose the supported return scope, and let Chrome save the requested PDF or Excel file locally.
git clone https://github.com/ComplyEaze/pack.git
cd pack
git checkout v0.5.1
nvm use
corepack enable
pnpm install --frozen-lockfile
pnpm run wxt:prepare
pnpm run compile
pnpm test
pnpm run build
pnpm run verify:package
Expected build output: .output/chrome-mv3. Load that
directory at chrome://extensions. The repository default
branch may differ from the tagged release; stay on the tag when
reproducing the tagged release.
Session storage clears when the extension is reloaded, updated, disabled, or the browser restarts. Local storage may retain install metadata, the active filed-return run lease, full-year ledger, target-review state, and the local demo manifest until cleared or removed.