From ccae585cf908b75cc0385164c67b733bdd580940 Mon Sep 17 00:00:00 2001 From: Javier Date: Thu, 30 Jul 2026 10:12:18 +0800 Subject: [PATCH] Update dev docs --- docs/devGuide/development/settingUp.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/devGuide/development/settingUp.md b/docs/devGuide/development/settingUp.md index 1c4266364a..bf3815ee3e 100644 --- a/docs/devGuide/development/settingUp.md +++ b/docs/devGuide/development/settingUp.md @@ -53,12 +53,12 @@ We recommend the **WebStorm IDE** or **VS Code** for working with MarkBind code. 1. **Bind your cloned version of MarkBind to your console** by navigating to the cloned `packages/cli` folder and running `npm link` - + -If the `markbind` command fails to execute with permission issues in the console, add execute permissions to the generated file in `packages/cli/dist/index.js` + If the `markbind` command fails to execute with permission issues in the console, add execute permissions to the generated file in `packages/cli/dist/index.js` -To prevent this from occurring, it is recommended to use the `dev`/`build:backend` scripts as described in [the workflow](workflow.md#editing-backend-features) - + To prevent this from occurring, it is recommended to use the `dev`/`build:backend` scripts as described in [the workflow](workflow.md#editing-backend-features) + 1. **Congratulations!** Now you are ready to start modifying MarkBind code.