feat: add new resources and documentation for VSCode and GitLens

- Introduced a new journal entry for September 25, 2025, linking to a Reddit discussion about GitLens features.
- Created documentation pages for GitLens and a guide on comparing files between branches in VSCode.
- Added an image asset for visual reference in the comparison guide.

Author: codekiln

assets/image_1758794025341_0.png

@@ -0,0 +1,4 @@
+## [[VSCode]]
+	- [Anyone else missing Branches and Commits with in Source Control? : r/vscode](https://www.reddit.com/r/vscode/comments/1gu94qp/anyone_else_missing_branches_and_commits_with_in/)
+		- > They can be enabled by clicking GitLens in the Source Control panel , clicking the three dots and selecting "Detach Branches View" (and other views as well).
+	- [[VSCode/How To/Diff a file with another branch]]

journals/2025_09_25.md

@@ -4,4 +4,35 @@ created-by:: [[Person/Alessandro Petrone]]
 
 - [aptrn/maxmsp-ts-example: Template Max Project with TypeScript and npm dependencies](https://github.com/aptrn/maxmsp-ts-example)
 	- > Template Max Project with TypeScript and npm dependencies
--
+	- ## [Bundle dependencies for Max](https://github.com/aptrn/maxmsp-ts-example?tab=readme-ov-file#bundle-dependencies-for-max)
+		- You can install dependencies using `pnpm i -D <package-name>`. If you're sure the dependency is [**compatible with Max**](https://github.com/aptrn/maxmsp-ts-example?tab=readme-ov-file#dependencies), you can add it to the config file.
+		  
+		  The configuration file `maxmsp.config.json` determines which dependencies are included in the compiled output. The default `output_path` is `lib`, placed as a subdirectory of the `outDir` found in the `tsconfig.json` file.
+		  
+		  You can manually edit the `maxmsp.config.json` file or use command-line scripts:
+		  
+		  ```
+		  pnpm maxmsp add <package-name> [--alias] [--path] [--files]
+		  ```
+		- `--alias`: Optional. Sets the prefix for the copied files. Default is the package name.
+		- `--path`: Optional. Sets the path to the package. Default is the package name.
+		- `--files`: Optional. Sets the files to copy. Default is `index.js`.
+		  
+		  Example:
+		  
+		  ```
+		  pnpm maxmsp add @not251/not251 --alias not251 --files "index.js, index.map.js"
+		  ```
+		  
+		  This will copy files:
+		- `node_modules/@not251/not251/dist/index.js`
+		- `node_modules/@not251/not251/dist/index.map.js`
+		  
+		  To:
+		- `lib/not251/not251_index.js`
+		- `lib/not251/not251_index.map.js`
+		  
+		  ---
+		  
+		  This project is heavily inspired by [TypeScript-for-Max](https://github.com/ErnstHot/TypeScript-for-Max) and uses [Max/Msp types at DefinitelyTyped](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/maxmsp)
+	-

pages/GitHub___aptrn___maxmsp-ts-example.md

@@ -0,0 +1,2 @@
+# [GitLens extension](https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens)
+	-

pages/VSCode___Extension___GitLens.md

@@ -0,0 +1,35 @@
+tags:: [[Diataxis/How To]]
+
+- # How To Compare a File with Another Branch in VS Code (GitLens)
+	- ## Goal
+		- View file differences between a file in your current branch and a file in another Git branch, similar to PyCharm’s *“Compare With Branch”* feature.
+	- ## Preconditions
+		- VS Code installed
+		- Git repository initialized
+		- [[VSCode/Extension/GitLens]]  installed
+	- ## Procedure
+		- ### 1. Enable Branches View in GitLens for the [[VSCode/Panel/Source Control]] Source Code panel
+			- Open **Source Control panel** (`Ctrl+Shift+G` / `Cmd+Shift+G`).
+			- Expand the **GitLens** section.
+			- Click the **three dots (…) menu**.
+			- Select **Detach Branches View**.
+				- This makes “Branches” appear as its own section.
+				- See also: [Anyone else missing Branches and Commits with in Source Control? : r/vscode](https://www.reddit.com/r/vscode/comments/1gu94qp/anyone_else_missing_branches_and_commits_with_in/)
+		- ### 2. Diff a Specific File with Another Branch
+			- In the **Branches** view, locate your current branch
+			- Click the disclosure triangle for `BRANCHNAME`
+			- Click on the pencil icon in the entry `Compare BRANCHNAME`
+			- Enter the branch name you wish to compare with
+			- You should now see an entry underneath like `DDD files changed AAA additions (+), DDD deletions (-)`; click the disclosure triangle
+			- Locate the specific file under the disclosure triangle you wish to compare, right click on it
+			- Navigate to **Open Changes with → Open Changes with Working File**.
+			- A side-by-side diff opens between your working copy and the file in the other branch.
+		- ### 3. Diff All Files with Other Branch
+			- Press on the `+/-` file button, which has the tooltip "Open All Changes as Working Tree"
+			- ![image.png](../assets/image_1758794025341_0.png)
+	- ## Gripes
+		- There's no way to bring over individual lines from one side of the diff to the other, the way there is in [[PyCharm]] or [[JetBrains]]
+	- ## Troubleshooting
+		- If Branches aren’t showing, check the GitLens menu → **Detach Branches View**.
+	- ## References
+		- Use the command palette (`Ctrl+Shift+P`) → **GitLens: Compare with Branch** for a repo-wide compare.