Site Refactoring (#720)

* chore(deps): bump dependencies & switch to pnpm

* feat: replace TutorialAuthors & Contributors by TutorialCredits

* feat: add prettier

* refactor: prettier

* fix: broken exponent

Author: wingkwong

.github/issue_template.md

@@ -4,12 +4,11 @@ If you want to request a topic on LeetCode The Hard Way
 
 - State the topic
 
-If you want to take the assignment as well 
+If you want to take the assignment as well
 
 - Suggest the markdown location
 - Suggest a few LC problems on this topic
 
+## Solution
 
-## Solution 
-
-You **DON'T** need to create an issue and ask for assignment. Just create a pull request. Issues created for solutions will be closed directly.
+You **DON'T** need to create an issue and ask for assignment. Just create a pull request. Issues created for solutions will be closed directly.

.github/pull_request_template.md

@@ -6,7 +6,7 @@ Provide summary of changes with issue number if any.
 
 **If you haven't fulfilled the below requirements or even delete the entire checklist, your PR won't be reviewed and will be closed without notice. Regular contributors (with 10+ PRs) can skip this part.**
 
-### General 
+### General
 
 - [ ] This Pull Request is all my own work. (You'll be blacklisted if you are caught for plagiarism.)
 - [ ] I've read [CONTRIBUTING.md](https://github.com/wingkwong/leetcode-the-hard-way/blob/main/CONTRIBUTING.md)
@@ -18,7 +18,7 @@ Provide summary of changes with issue number if any.
 ### Tutorial
 
 - [ ] I've read and followed the [Tutorial Template](https://github.com/wingkwong/leetcode-the-hard-way/blob/main/CONTRIBUTING.md#tutorial-template)
-- [ ] I've explained my topic well with 2 - 3 LC problems and no external problems are used. 
+- [ ] I've explained my topic well with 2 - 3 LC problems and no external problems are used.
 - [ ] I've provided the full working solutions to the problems used in this tutorial.
 - [ ] I've provided suggested problems at the end with the given format. See [here](https://raw.githubusercontent.com/wingkwong/leetcode-the-hard-way/main/tutorials/math/number-theory/binary-exponentiation.md) as an example. If the target solution is not available, leave `solutionLink` blank.
 - [ ] I've given credits / references if I use external resources. (For an image, give credit under it. Otherwise, add a new section called References at the end (after Suggested Problems).)

.github/workflows/deploy.yml

@@ -36,4 +36,3 @@ jobs:
           # https://github.com/actions/checkout/issues/13#issuecomment-724415212
           user_name: wingkwong
           user_email: [email protected]
-

.prettierrc

@@ -0,0 +1,7 @@
+{
+  "bracketSameLine": false,
+  "printWidth": 80,
+  "proseWrap": "never",
+  "singleQuote": true,
+  "trailingComma": "all"
+}

CONTRIBUTING.md

@@ -6,49 +6,46 @@ Don't reply on markdown editor. Start the application locally to make and verify
 
 ```bash
 cd leetcode-the-hard-way
-npm i 
+npm i
 npm run start
 # By default, a browser window will open at http://localhost:3000/.
 ```
 
-## Before Creating a PR 
+## Before Creating a PR
 
 See the [Checklist](https://github.com/wingkwong/leetcode-the-hard-way/blob/main/.github/pull_request_template.md#checklist).
 
 ## Tutorial Template
 
 Tutorials markdown files are stored under `./tutorials`.
 
-````md
+```md
 ---
 title: '<TITLE>'
 description: '<DESCRIPTION_OF_THE_TOPIC>'
 hide_table_of_contents: true
 ---
 
-<TutorialAuthors names="@<YOUR_ALIAS>"/>
+<TutorialCredits authors="@<YOUR_ALIAS>"/>
 
 ## Overview
 
 // TODO: Overview of the topic
 
-// DO NOT COPY FROM OTHER EXTERNAL SITES
-// DO NOT USE RANDOM EXAMPLES OR EXAMPLES FROM OTHER SITES
+// DO NOT COPY FROM OTHER EXTERNAL SITES // DO NOT USE RANDOM EXAMPLES OR EXAMPLES FROM OTHER SITES
 
-// TODO: Complexity Analysis
-// TODO: Walk through the topic using 2 - 3 LC problems
+// TODO: Complexity Analysis // TODO: Walk through the topic using 2 - 3 LC problems
 
-### Example : [<PROBLEM_ID> - <PROBLEM_TITLE>](<LC_LINK>)
+### Example : [<PROBLEM_ID> - <PROBLEM_TITLE>](LC_LINK)
 
 > <PROBLEM STATEMENT>
 
-// TODO: Your explanation
-// TODO: Your solution to the problem
+// TODO: Your explanation // TODO: Your solution to the problem
 
 // TODO: add Suggested Problems (See the examples below to learn how to render)
-````
+```
 
-Examples: 
+Examples:
 
 - [binary-exponentiation.md](https://raw.githubusercontent.com/wingkwong/leetcode-the-hard-way/main/tutorials/math/number-theory/binary-exponentiation.md)
 
@@ -60,13 +57,11 @@ Examples:
 - File name format: `<PROBLEM_ID>-<PROBLEM_TITLE>-<DIFFICULTY>.md`, e.g. `0202-happy-number-easy.md`
 
 ````md
-// The Meta and Problem Statement can be generated by using a Chrome extension under `converter` locally. 
-// If you do not know how to do it, leave it blank and @wingkwong will help add them.
+// The Meta and Problem Statement can be generated by using a Chrome extension under `converter` locally. // If you do not know how to do it, leave it blank and we will help add them.
 
 ## Approach 1: <APPROACH_NAME>
 
-// TODO: Detailed Explanations / Line by Line Explanations in code
-// TODO: Complexity Analysis
+// TODO: Detailed Explanations / Line by Line Explanations in code // TODO: Complexity Analysis
 
 <Tabs>
 <TabItem value="cpp" label="C++">
@@ -97,8 +92,7 @@ Examples:
 
 ## Approach 2: <APPROACH_NAME> (ADD IT IF NECESSARY)
 
-// TODO: Detailed Explanations / Line by Line Explanations in code
-// TODO: Complexity Analysis
+// TODO: Detailed Explanations / Line by Line Explanations in code // TODO: Complexity Analysis
 
 <Tabs>
 <TabItem value="cpp" label="C++">
@@ -128,7 +122,7 @@ Examples:
 </Tabs>
 ````
 
-Examples: 
+Examples:
 
 - [0191-number-of-1-bits-easy.md](https://raw.githubusercontent.com/wingkwong/leetcode-the-hard-way/main/solutions/0100-0199/0191-number-of-1-bits-easy.md)
 
@@ -138,4 +132,4 @@ Examples:
 
 - If your content includes variables or math equations, please highlight it with LaTex syntax. See [binary-exponentiation.md](https://raw.githubusercontent.com/wingkwong/leetcode-the-hard-way/main/tutorials/math/number-theory/binary-exponentiation.md) as an example.
 
-- If you have used other resources from external sites, give references at the end.
+- If you have used other resources from external sites, give references at the end.

README.md

@@ -2,7 +2,7 @@
 
 <img align="left" width="240" height="360" src="https://user-images.githubusercontent.com/35857179/168307611-1b28018b-fc98-4cff-88a6-d8312ac7bce6.png">
 
-## About 
+## About
 
 Welcome to "LeetCode The Hard Way," the ultimate resource for those looking to improve their skills in data structures and algorithms! Our website is dedicated to providing comprehensive tutorials and detailed solutions to some of the most challenging problems in LeetCode. Whether you're a student looking to ace your next exam or a professional seeking to level up your coding skills, our tutorials and solutions are designed to help you succeed. Our content covers a range of popular programming languages, so you can learn and practice using the language of your choice.
 

config.json

@@ -1,11 +1,11 @@
 {
-    "index_name": "leetcode-the-hard-way",
-    "start_urls": ["https://leetcodethehardway.com/"],
-    "selectors": {
-      "lvl0": "",
-      "lvl1": "h1",
-      "lvl2": "h2",
-      "lvl3": "h3",
-      "text": "article div,article p,article theme-code-block"
-    }
-}
+  "index_name": "leetcode-the-hard-way",
+  "start_urls": ["https://leetcodethehardway.com/"],
+  "selectors": {
+    "lvl0": "",
+    "lvl1": "h1",
+    "lvl2": "h2",
+    "lvl3": "h3",
+    "text": "article div,article p,article theme-code-block"
+  }
+}

converter/README.md

@@ -1,3 +1,3 @@
 # LeetCode The Hard Way - Converter
 
-Chrome Extension to convert LeetCode problems into LTHW format. Originally work is done by [crx-leetmark](https://github.com/crimx/crx-leetmark).
+Chrome Extension to convert LeetCode problems into LTHW format. Originally work is done by [crx-leetmark](https://github.com/crimx/crx-leetmark).

converter/background.js

@@ -1,9 +1,8 @@
 chrome.runtime.onMessage.addListener((msg, sender, sendResponse) => {
-    switch (msg.type) {
-      case 'page_action_show':
-        if (sender.tab && sender.tab.id)
-        chrome.pageAction.show(sender.tab.id)
-        sendResponse()
-        return
-    }
-  })
+  switch (msg.type) {
+    case 'page_action_show':
+      if (sender.tab && sender.tab.id) chrome.pageAction.show(sender.tab.id);
+      sendResponse();
+      return;
+  }
+});