Node 24 support

.gitignore

@@ -10,8 +10,6 @@
 
 # production
 /build
-/build-ios/WebViewExample/local_html
-/build-electron
 /dist
 
 # misc

.nvmrc

@@ -1 +1 @@
-14
+24

.svgrrc.js

@@ -0,0 +1,29 @@
+module.exports = {
+  jsxRuntime: 'classic',
+  plugins: ['@svgr/plugin-jsx'],
+  svgoConfig: {
+    plugins: [
+      {
+        name: 'preset-default',
+        params: {
+          overrides: {
+            removeViewBox: false,
+          },
+        },
+      },
+    ],
+  },
+  jsx: {
+    babelConfig: {
+      plugins: [
+        [
+          '@babel/plugin-transform-react-jsx',
+          {
+            throwIfNamespace: false,
+            useBuiltIns: true,
+          },
+        ],
+      ],
+    },
+  },
+};

README.md

@@ -43,7 +43,7 @@ Then run the version command at the end as a check. If you would like to install
 ### 3. Node Version Manager
 <sup>(nvm = Node Version Manager)</sup>
 
-nvm is a CLI library that helps you manage the Node versions you have installed on your device. You should be able to [install Node versions directly from online](<https://nodejs.org/en/download>), but as we're going for a specific older version and to be more organized, we recommend installing nvm. 
+nvm is a CLI library that helps you manage the Node versions you have installed on your device. You should be able to [install Node versions directly from online](<https://nodejs.org/en/download>).
 Run a quick nvm check to see if you have it installed—
 ```
 nvm ls
@@ -60,32 +60,13 @@ which downloads the nvm code to an nvm directory on your system. Try running `nv
 
 <sup>If you're on Windows, please see [nvm-windows](https://github.com/coreybutler/nvm-windows).</sup>
 
-### 4. Installing Node v14
-Wick Editor is a software that hasn't been updated in ~5 years before we picked it back up with our fork.
-For that reason though, it requires an older version of Node. 
+### 4. Installing Node
+Wick Editor uses the active version of Node, 24.
 
-Try first running this command to install Node v14: 
+Ensure you're on the correct Node version using `nvm`: 
 ```
-nvm install 14
+nvm install 24
 ```
-There's a chance this works, and if it does you may move on to the next step.
-If it doesn't work, and you're on a Mac device with an M-series chip, the issue is likely because Node v14 doesn't have ARM64 support, so you'll likely need to install [Rosetta 2](<https://github.com/nodejs/node/issues/52306#issuecomment-2031073649>) to work around this issue.
-```
-/usr/sbin/softwareupdate --install-rosetta --agree-to-license
-```
-Then use it to change the arch
-```
-arch -x86_64 zsh
-```
-Then re-run nvm install.
-```
-nvm install 14
-```
-<sup>For anyone on Windows, you won't need this step</sup>
-
-Things usually get resolved after this. If you still have an error, let us know what it says.
-
-**Side Note:** When nvm installs v14, it uses it by default. You can run `nvm ls` to check that it is, if you don't see an arrow next to version `14._._` then run `nvm use 14` and re-check.
 
 ### 5. Final step, setup and run
 You need to navigate to your project file... if you don't know how to navigate through the terminal then you may use [this online video tutorial](<https://www.youtube.com/watch?v=5XgBd6rjuDQ>) to learn how. It's simple but takes a minute to explain.
@@ -101,13 +82,6 @@ If you have the repository set up, then navigate to the directory and run the fo
 ```
 npm install
 ```
-<sup>(If at any point you switched terminals, please make sure you're still using npm v14 before running the last command, `npm install`. To ensure you're using npm v14, you may run `nvm use 14`, if you have nvm set up successfully)</sup>
-
-You may see a few warnings, like ummmm... a little over 300... due to the outdated packages... but don't worry about em' 😅 As long as things download successfully, it's fine.
-
-<sup>Programming rule #1, if things work, don't touch it... don't worry though those are things we're slowly fixing</sup>
-
-If the terminal says something like `found 0 vulnerabilities` after only 7 lines of loading or such, then there's a change you're in the wrong directory.
 
 Once you have everything setup, all you need to do to test your app is... first build the engine:
 ```