fix: anchor links (#136)

.husky/pre-commit

@@ -1,4 +1 @@
-#!/bin/sh
-. "$(dirname "$0")/_/husky.sh"
-
-npx lint-staged
+bun lint-staged

docs/development/api-wrapper/classes/context-menu.md

@@ -156,7 +156,7 @@ addItem(item: Item): void
 
 | Parameter | Type | Description |
 | :--- | :--- | :--- |
-| item | [`Item`](/docs/development/api-wrapper/classes/context-menu/#item) | `Item` to be added to the sub menu. |
+| item | [`Item`](#item) | `Item` to be added to the sub menu. |
 
 ##### `removeItem`
 
@@ -168,7 +168,7 @@ removeItem(item: Item): void
 
 | Parameter | Type | Description |
 | :--- | :--- | :--- |
-| item | [`Item`](/docs/development/api-wrapper/classes/context-menu/#item) | `Item` to be removed from the sub menu. |
+| item | [`Item`](#item) | `Item` to be removed from the sub menu. |
 
 ##### `register`
 

docs/development/api-wrapper/methods/local-storage.md

@@ -9,7 +9,7 @@ Spicetify provides a wrapper for `localStorage` to make it easier to use.
 
 All keys created via this method is generic and stored as-is.
 
-If you wish to store values that are specific for each user account, you can use [`Platform.LocalStorageAPI`](/docs/development/api-wrapper/methods/platform#localstorage) instead.
+If you wish to store values that are specific for each user account, you can use [`Platform.LocalStorageAPI`](/docs/development/api-wrapper/methods/platform#localstorageapi) instead.
 
 :::
 

docs/development/custom-apps.md

@@ -120,7 +120,7 @@ Spicetify.Platform.History.push({
 });
 ```
 
-In order to render a different page, you can check the `pathname` of the current page within `index.js`'s main render method, and render a different page component for different paths. The main path for your custom app will be the name of the folder (which is the same that needs to be used in the [`config-xpui.ini`](./themes#configs) configuration file).
+In order to render a different page, you can check the `pathname` of the current page within `index.js`'s main render method, and render a different page component for different paths. The main path for your custom app will be the name of the folder (which is the same that needs to be used in the [`config-xpui.ini`](/docs/development/themes) configuration file).
 In this example, if our `pathname` is "/marketplace/readme", we load the `ReadmePage` component, otherwise we load our main page component, `Grid`.
 
 ```js

package.json

@@ -13,7 +13,7 @@
     "serve": "docusaurus serve",
     "write-translations": "docusaurus write-translations",
     "write-heading-ids": "docusaurus write-heading-ids",
-    "prepare": "husky install"
+    "prepare": "husky"
   },
   "dependencies": {
     "@algolia/client-search": "^4.23.2",
@@ -48,6 +48,6 @@
     "typescript": "^5.4.4"
   },
   "lint-staged": {
-    "*.js|ts|jsx|tsx": "biome check --apply"
+    "*": "biome check --apply"
   }
 }