Skip to content

Update dev docs #2910

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Incogdino merged 1 commit into from
Jul 30, 2026
+4 −4
Merged

Update dev docs #2910

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/devGuide/development/settingUp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`

<box type="warning" class="ms-4" seamless>
<box type="warning" class="ms-4" seamless>

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)
</box>
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)
</box>

1. **Congratulations!** Now you are ready to start modifying MarkBind code.

Expand Down
Loading