Open Issues Need Help
View All on GitHubAI Summary: The `checkSafariMagicBytes` function currently reads the entire cookie file into memory to check for a 4-byte magic signature. This is inefficient as only the first 4 bytes are needed. The recommended solution is to use `fs.openSync` and `fs.readSync` to read only the necessary 4 bytes, significantly reducing I/O costs.
🍪🖐 Node.js tool for querying local browser Chrome, Firefox or Safari cookies
AI Summary: This issue addresses code duplication where the `getBrowserDisplayName` function and its associated browser name mapping are defined identically in two separate files. The proposed solution is to remove one of the definitions and import the function from the other file, thus consolidating the logic and preventing maintenance issues when new browsers are added.
🍪🖐 Node.js tool for querying local browser Chrome, Firefox or Safari cookies
AI Summary: The `EnhancedCookieQueryService` currently throws an "not yet implemented" error when its `discoverBrowserFiles()` method is called. This prevents the service from automatically finding browser cookie files, forcing users to manually specify file paths and negating its "enhanced" auto-discovery capability.
🍪🖐 Node.js tool for querying local browser Chrome, Firefox or Safari cookies
AI Summary: This issue requests adding unit tests for six public functions within the `StrategyFactory.ts` module. Currently, these functions lack test coverage, which could lead to regressions if the `STRATEGY_REGISTRY` is modified in the future. The proposed solution involves verifying return types, strategy counts, and fallback behavior without requiring actual browser interaction.
🍪🖐 Node.js tool for querying local browser Chrome, Firefox or Safari cookies