Skip to content

A Chrome Extensions to help LeetCode users keep track of LeetCode failed questions

License

Notifications You must be signed in to change notification settings

architec/mistake

This branch is 186 commits ahead of, 31 commits behind lxieyang/chrome-extension-boilerplate-react:master.

Folders and files

NameName
Last commit message
Last commit date
Jan 6, 2022
Jul 20, 2019
Oct 23, 2021
Nov 18, 2021
Oct 2, 2023
Oct 2, 2023
Feb 21, 2021
Jul 20, 2019
Oct 23, 2021
Nov 29, 2019
Dec 10, 2021
Oct 23, 2021
Jul 20, 2019
Oct 24, 2021
Dec 10, 2021
Jul 25, 2019
Oct 18, 2023
Oct 23, 2021
Oct 19, 2024
Aug 30, 2024
Oct 27, 2020
Feb 21, 2021

Repository files navigation

LeetCode Mistake Tracker Chrome Extension

Docker Image CI Chrome Web Store users

This is a Chrome Extensions to help LeetCode users keep track of the LeetCode questions they would like to re-do in the future.

After users specified time period, the extension will remind the users to re-do the LeetCode question selected.

Q: Why didn't I use the "add to list" feature from LeetCode?

A: I would like to sort the questions by the time when it was added, and give me an alert when my reminder time is up, to re-do this LeetCode question. I didn't find any similar feature from "add to list", so I created a chrome extension for this specific feature.

User Installation

Install the extension from here

Features

This Chrome Extension currently supports:

  • Save the re-do LeetCode questions

redo.png

  • Show the list of LeetCode questions by extension popup

popup.png

Developer Installing and Running

Procedures (Docker)

  1. Check if your Node.js version is >= 14.
  2. Clone this repository.
  3. Run npm run compose
  4. Load your extension on Chrome following:
    1. Access chrome://extensions/
    2. Check Developer mode
    3. Click on Load unpacked extension
    4. Select the build folder.
  5. Happy hacking.

Build by NPM

For step 3 above, you can use the following steps instead

  1. Run npm install to install the dependencies.
  2. Run npm start

Packing

After the development of your extension run the command

$ NODE_ENV=production npm run build

Now, the content of build folder will be the extension ready to be submitted to the Chrome Web Store. Just take a look at the official guide to more infos about publishing.

Credits

Languages

  • JavaScript 83.9%
  • CSS 9.5%
  • HTML 3.2%
  • TypeScript 1.7%
  • Dockerfile 1.5%
  • SCSS 0.2%