Why cache namespaces?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start by tracing the browser localStorage path that loads enabled namespaces, then compare it with the debug.store behavior and the VITE_DEBUG_ENABLE initialization shown in the issue. The issue names no files or tests; completion depends on deciding the intended cache behavior and confirming it across page loads.
Written by the indexing model from the issue text.
Description
I do not understand why localstorage is used to cache the enabled namespaces. It seems to just cause confusion with unexpected behavior. #901 #536 #871 #534 #337
I had to spend some time to figure out why
if (process.env.VITE_DEBUG_ENABLE)
debug.enable(process.env.VITE_DEBUG_ENABLE);
didn't work when I removed the env var. I expected each page load to be an isolated environment until I managed to step through the code and see its caching. I tried to disable storage with debug.store = null but that didn't prevent the initial load.
debug.enable(process.env.VITE_DEBUG_ENABLE ?? '');
is where I landed, which admittedly isn't complicated, but its weird that I had to deal with this problem.
- Dominant language
- JavaScript
- Stars
- 11.5k
- Forks
- 992
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from debug-js/debug
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Debug as JSON Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 28/100
Similar issues
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AllTheMods/ATM-10-L#19 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SignalK/n2k-signalk#345 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
JuliaPluto/PlutoPlotly.jl#72 ·