LeetPrep - Handy Interview Preparation for Developers

What is LeetPrep?

LeetPrep is a handy interview preparation tool for developers. It contains the most commonly used resources to prepare for tech interviews.

• Programming Languages Documentation (Python, Java)
• References to built-in functions and data structures with examples.
• Big O complexity tables and charts (Data Structures & Sorting)
• Common problem-solving techniques for Leetcode (Leetcode Patterns)
• Quick access to a curated list of popular interview questions (Blind 75)

Having easy access to a curated set of resources is very useful while doing leetcode problems or simply studying for interviews. The one click access to the handy resources is a massive improvement for preparation!

Star this repository for further development of features. If you want a particular feature, simply request for it!

Contributing

LeetPrep is a fully open-source project and contributions are welcome to improve the extension.

Here are a few feature opens you can get started with:

• Additional Programming Languages Documentation
  • C++
  • Javascript
  • Ruby
  • C#
  • Go
• SQL Documentation
• Data Science Section
  • Pandas Documentation
  • Numpy Documentation
• Add difficulty level to Blind 75 questions

If you have any other new suggestions or feature requests, feel free to open an issue or submit a pull request.

Local Development

1. Fork this repo and clone to your local machine
2. Go to chrome://extensions
3. Enable Developer mode by toggling the switch on top right corner
4. Click 'Load unpacked'
5. Select the "build" folder at the root of this repo
6. Local development extension should be loaded now

Commands available:

npm i                 Install dependencies
npm run start         Start the development server at localhost
npm run build         Publish production ready extension to the build folder

When installing node modules, if there is a dependency errror, run npm config set legacy-peer-deps true then run npm i.

Commit Convention

Before you create a Pull Request, please check that you use the conventional commits format.

It should be in the form category(scope or module): message in your commit message from the following categories:

• feat / feature: all changes that introduce completely new code or new features

• fix / bug: all changes that fix a bug

• refactor: any code related change that is not a fix nor a feature

• docs: changing existing or creating new documentation (i.e. README, docs for usage of a lib or cli usage)

• chore: all changes to the repository that do not fit into any of the above categories

  e.g. feat(editor): improve tab switching speed