fix(tools): improve development run-scripts

Author: raisedadead

package.json

@@ -4,14 +4,10 @@
   "version": "1.0.0",
   "private": true,
   "scripts": {
-    "preinstall": "npx only-allow pnpm",
-    "prepare": "npx is-ci || npx husky",
-    "dev": "pnpm run develop",
+    "prepare": "is-ci || husky",
     "develop": "astro dev",
-    "start": "node ./run-server.mjs",
-    "build": "rm -rf ./dist && astro check && astro build",
-    "preview": "wrangler pages dev ./dist",
-    "astro": "astro",
+    "build": "astro build",
+    "preview": "pnpm build && wrangler pages dev",
     "format": "prettier . --write --cache && eslint . --cache --fix",
     "lint": "prettier . --check --cache && eslint . --cache",
     "playwright:run": "playwright test",
@@ -22,7 +18,7 @@
       "pnpm format"
     ],
     "**/*.{mdx,md}": [
-      "npx prettier . --write"
+      "pnpm exec prettier . --write"
     ]
   },
   "dependencies": {
@@ -48,7 +44,7 @@
     "husky": "9.1.7",
     "is-ci": "4.1.0",
     "lint-staged": "16.1.2",
-    "prettier": "3.5.3",
+    "prettier": "3.6.2",
     "prettier-plugin-astro": "0.14.1",
     "sharp": "0.34.2",
     "wrangler": "^4.0.0"

pnpm-lock.yaml

@@ -93,7 +93,6 @@ Some examples of good PR titles would be:
 3.  Submit the pull request from your branch to freeCodeCamp's `main` branch.
 
 4.  Include a more detailed summary of the changes you made and how your changes are helpful in the body of your PR.
-
     - You will be presented with a pull request template. This is a checklist that you should have followed before opening the pull request.
 
     - Fill in the details as you see fit. Ensure that you give the reviewers enough context to review the changes. If the PR makes changes to the UI, be sure to include screenshots of the changes as well. All of this information will be reviewed and the reviewers will decide whether or not your pull request is accepted.
@@ -104,7 +103,6 @@ Some examples of good PR titles would be:
       > Example: `Closes #123` will close issue 123
 
 5.  Indicate if you have tested on a local copy of the site or not.
-
     - This is very important when making changes that are not just edits to text content like documentation or a challenge description. Examples of changes that need local testing include JavaScript, CSS, or HTML, which could change the functionality or layout of a page.
 
     - If your PR affects the behavior of a page, it should be accompanied by corresponding [Playwright integration tests](/how-to-add-playwright-tests/).

src/content/docs/how-to-open-a-pull-request.mdx

@@ -117,7 +117,6 @@ We have automated the process of installing all the dependencies & tools you wil
    and you should see a workspace created for you. This works for any repository or pull-request on GitHub.
 
 2. Alternatively install one of the below extensions for your browser.
-
    - [Chrome Webstore](https://chrome.google.com/webstore/detail/gitpod-always-ready-to-co/dodmmooeoklaejobgleioelladacbeki) - works with Chromium-based browsers like Google Chrome, Brave, Edge, etc.
    - [Firefox Add-on](https://addons.mozilla.org/en-US/firefox/addon/gitpod) - Firefox
 

src/content/docs/how-to-setup-freecodecamp-locally.mdx

@@ -39,7 +39,6 @@ We just ask that you understand the following:
    For example, we would want to deploy at least the first 3 certifications when we ship a new world language for the first time.
 
    The directories on Crowdin containing the first 3 certifications are:
-
    - 14-responsive-web-design-22
    - 15-javascript-algorithms-and-data-structures-22
    - 03-front-end-development-libraries

src/content/docs/how-to-translate-files.mdx

@@ -29,11 +29,9 @@ Most of the files for translating the platform are located in the [`client/i18n`
 - config
   - i18n.ts
 - i18n
-
   - configForTests.js
   - config.js
   - locales
-
     - **chinese** _Name of the world language_
       - intro.json
       - links.json

src/content/docs/how-to-work-on-localized-client-webapp.mdx

@@ -286,7 +286,6 @@ Camperbot serves as our moderation bot, and all of the commands use Discord's na
 3. **Creating a private discussion**
 
    There may be situations where you need to address a concern with a camper privately. This should not be done through DMs, which can lead to situations where you claim one thing and the camper claims another. Instead, use the bot's functionality to create a private discussion:
-
    - Call the `/private` command, where `target` is the camper you want to open a private channel with.
    - The bot will create a new channel, and add the mentioned camper and all moderators with the `Your Friendly Moderator` role. While all moderators are added to the channel for transparency, the moderator who calls this command should be the only one to interact with the camper unless they request assistance.
    - When the conversation is complete, click the `❌ Close` button _on the first message in the private channel_ to have the bot close and delete that channel.
@@ -306,7 +305,6 @@ Camperbot serves as our moderation bot, and all of the commands use Discord's na
    If a violation was clearly unintended and doesn't warrant moderation action or private conversation, make the offending camper aware of their actions without making it come across as a warning.
 
    For example:
-
    - Camper posts a wall of code to request help:
 
      Moderator: **@username** Please use CodePen or Pastebin when posting large amounts of code.

src/content/docs/moderator-handbook.mdx

@@ -0,0 +1,7 @@
+# Generated by Wrangler on Tue Jul 08 2025 11:51:51 GMT+0530 (India Standard Time)
+name = "contribute"
+pages_build_output_dir = "dist"
+compatibility_date = "2024-11-11"
+
+[placement]
+mode = "smart"