Dwtexe/cursor-stats v1.1.3

v1.1.3 - Emergency Hotfix: Token Retrieval & SQLite Revert

on GitHub

• Reverted the SQLite library from node-sqlite3-wasm back to sql.js (as used in v1.1.1 and earlier).
• This fixes a critical bug introduced in v1.1.2 that prevented some users (especially on Macos) from retrieving their access token, rendering the extension unusable for them.

• Users who experienced errors fetching their token with v1.1.2 should find this version resolves the problem.

• The previous attempt in v1.1.2 to address issues with very large state.vscdb files (over 2GB) using node-sqlite3-wasm had to be rolled back due to the token retrieval bug it introduced.
• Temporary Workaround for 2GB+ Database Issue (if you encounter it with sql.js):
  1. Download a SQLite browser.
  2. Make a backup copy of your state.vscdb file.
  3. Open the copy with the SQLite browser.
  4. The table containing chat history and other non-essential data is typically named cursorDiskKV. The table with your auth token is ItemTable.
  5. Delete the cursorDiskKV table (or other large tables, keeping ItemTable intact) to reduce the database file size.
  6. In Cursor, go to extension settings for "Cursor Stats" and use the "Custom Database Path" (cursorStats.customDatabasePath) option to point the extension to your modified (smaller) database file copy.
• This workaround allowed users with huge database files to use the extension before the v1.1.2 changes and should still be viable.

Buy Me A Coffee

Binance

• ID: 39070620

USDT

• Multi-Chain (BEP20/ERC20/Arbitrum One/Optimism):

  0x88bfb527158387f8f74c5a96a0468615d06f3899
  

• TRC20:

  TPTnapCanmrsfcMVAyn4YiC6dLP8Wx1Czb