bangarharshit / bangarharshit/spot

Moving to non-persistent background script

Open
#6 0 comments 0 reactions 0 assignees View on GitHub
enhancement good first issue
Dominant language
JavaScript
Stars
3
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Currently, the extension is persistent so it always runs even if nothing is happening. As a result, everything is a global variable.

Move it to non-persistent. Tried doing it but turned out to be trickier than I thought. Here is the migration guide -
https://developer.chrome.com/extensions/background_migration

@chetdeva this needs a serious architecture thinking (currently there is none - thanks to global variables) so let us jam and feel free to dump your thought.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with Chrome's background migration guide and inspect the extension's background script and its global variables. Map which state currently depends on the persistent process before proposing the architecture. Done means the extension runs as a non-persistent background script without relying on process-lifetime globals.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
web-dev
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.