chore: update packages (#231)

svrnm · Nov 21, 2024 · 24edf4c · 24edf4c
1 parent abe39b6
commit 24edf4c
Show file tree

Hide file tree

Showing 23 changed files with 639 additions and 1,295 deletions.
diff --git a/.babelrc b/.babelrc
@@ -1,4 +1,4 @@
 {
   "presets": ["@babel/preset-react", "@babel/preset-env"],
-  "plugins": ["@babel/plugin-proposal-class-properties", "@babel/plugin-transform-runtime"]
+  "plugins": ["@babel/plugin-transform-class-properties", "@babel/plugin-transform-runtime"]
 }
diff --git a/.prettierignore b/.prettierignore
@@ -1,2 +1,4 @@
 build
 node_modules
+# the template triggers an error because of the code within the <html 
+pages/template.html
diff --git a/README.md b/README.md
@@ -1,17 +1,5 @@
 # <img src="icons/monkey.png" alt="DemoMonkey Icon" width="28" height=""> DemoMonkey
 
-> [!IMPORTANT]
-> DemoMonkey needs your help!
->
-> Since switching from Manifest V2 to Manifest V3, DemoMonkey is experiencing an ongoing issue with storing configurations.
-> We explored multiple options to fix this issue, but none of them worked out.
->
-> It looks like the only way to fix this issue is to overhaul the whole the storage mechanism as the current implementation
-> is not compatible with Manifest V3. This is a huge effort and we need your help to make it happen.
->
-> If you have bandwidth, experience with JavaScript (and maybe even building Chrome Extensions) and the interest to help, please let us now
-> by commenting on [this issue](https://github.com/svrnm/DemoMonkey/issues/131).
-
 ## About
 
 DemoMonkey allows you to turn your software demo in a fully tailored demo for your prospect in minutes:

diff --git a/manifest.json b/manifest.json
@@ -2,7 +2,7 @@
   "manifest_version": 3,
   "name": "DemoMonkey",
   "description": "Custom demo, every demo: Turn your standard demo into a tailored experience for your customers in minutes.",
-  "version": "9.1.0",
+  "version": "9.2.0",
   "author": "Severin Neumann <[email protected]>",
   "homepage_url": "https://github.com/svrnm/DemoMonkey/",
   "content_security_policy": {