chore: update @types/node and @comapeo/core

package.json

@@ -49,7 +49,7 @@
 		"vite:build": "vite build src/renderer"
 	},
 	"dependencies": {
-		"@comapeo/core": "2.0.1",
+		"@comapeo/core": "2.1.0",
 		"@comapeo/ipc": "2.0.2",
 		"@formatjs/intl": "^2.10.11",
 		"@mapeo/default-config": "5.0.0",
@@ -87,7 +87,7 @@
 		"@tanstack/react-query": "^5.59.16",
 		"@types/eslint__js": "^8.42.3",
 		"@types/lint-staged": "^13.3.0",
-		"@types/node": "^20.17.4",
+		"@types/node": "^20.17.5",
 		"@types/react": "^18.3.12",
 		"@types/react-dom": "^18.3.1",
 		"@types/sodium-native": "^2.3.9",

patches/README.md

@@ -5,7 +5,7 @@ fixes.
 
 ## @comapeo/core
 
-### [Do not watch fallback map patch when setting up SMP server plugin](./@comapeo+core+2.0.1+001+fix-smp-fallback-map-setup.patch)
+### [Do not watch fallback map patch when setting up SMP server plugin](./@comapeo+core+2.1.0+001+fix-smp-fallback-map-setup.patch)
 
 By default, core sets up a file watcher for the `fallbackMapPath` option that's provided when instantiating `MapeoManager`. This does not work when packaging the app as an ASAR file (via Electron Forge) because watching a file within the ASAR directory is not possible. Instead, we change the setup so that it does not try to watch the file and instead make the assumption that the file always exists on instantiation, which is generally the case in CoMapeo Desktop (for now).