Contains my leetcode solutions.
I don't like coding in a browser so I added tools to support local development:
- Generate a solution file for the problem, with the problem description and blank code snippet.
- Generate the test file and test cases for the problem.
- Minify a problems source code and copy to clipboard so it can be submitted easily.
- Reset the source of a previously solved problem so it can be practiced.
Clone the repository and install the packages:
git clone https://github.com/beakerandjake/leetcode
cd leetcode
npm installRun the tests for all problems:
npm run testRun the test for a specific problem
npm run test 42Create the source and test file for the specified problem, commits these files to git, and finally opens them in vs code.
The source file is added to src/ and test file is added to tests/.
An attempt is made to scrape the inputs and expected outputs from each example in the problem description. If scraping is successful a test case will be generated for each example and will provide the function with the correct inputs and test the result against the expected output. This process is not always successful so be sure to double check the generated test.
To touch the daily question, invoke with no arguments:
npm run touchIf touch is invoked with an argument, it should be either the problem slug or the full problem url.
The problem slug is located in the problems url leetcode.com/problems/SLUG/...
To touch problem #1 (https://leetcode.com/problems/two-sum) using the problem slug:
npm run touch two-sumTo touch problem #1 (https://leetcode.com/problems/two-sum) using the full url:
npm run touch https://leetcode.com/problems/two-sumAdditionally you can use the --reset flag to clear the existing source code for the problem. This is helpful if you want to practice the implementation.
npm run touch two-sum -- --resetNote the -- is necessary to tell npm that the --reset flag is not for npm but for the touch command.
Uglifies the problem source code outputs it to the console and attempts to copy it to the clipboard (if xclip is installed on the system).
You can paste this output into the leetcode editor and submit your solution.
To uglify problem 42:
npm run uglify 42Any additional arguments you pass to this command will be forwarded to uglify.js.
For example to tell uglify-js to not mangle quoted property names:
npm run uglify 42 -- --mangle-props keep_quotedReturns information about the specified problem, including the difficulty and number of likes/dislikes. Can optionally include the tags of the problem.
If provided no arguments, will return information about the problem of the day.
To get the info about a specific problem use the problem slug or url:
npm run info two-sumnpm run info https://leetcode.com/problems/two-sumTo include the tags in the output, use the --tags option:
run info https://leetcode.com/problems/two-sum -- --tagsReturns the total number of problems that are in the src/ folder.
npm run countReturns the total number of problems that were created today.
npm run todayReturns the number of problems solved out of the book Cracking the Coding Interview
Note this isn't a perfect mapping, and a lot of problems in the book don't map to a leetcode problem, additionally I may have missed some problems while mapping.
npm run ctciAdditionally you can pass the --remaining flag to list the remaining problems:
npm run ctci -- --remainingIf you have leetcode premium and wish to use the touch command with premium problems, you will need to authenticate.
Create an .env file at the root of the repository. Add an environment variable named LEETCODE_SESSION_TOKEN with the value set to your leetcode session cookie.
echo 'LEETCODE_SESSION_TOKEN=YOURTOKENHERE' > .envThis file should not be committed to source control. It is ignored by default in the .gitignore
Big thanks to the leetcode-query package, it removed a lot of the copy and paste tedium when creating the source files for problems.