frontend/src/models/admin.js

It's a good practice to not expose the actual error message to the client. Instead, log the error message and send a generic error message to the client. This prevents potential attackers from gaining insights into the internal workings of your application.
Create Issue

    .catch((e) => {
+      console.error(e);
+      return { success: false, error: 'An error occurred while processing your request.' };
-      return null;
    });

It's a good practice to use meaningful variable names. This makes the code easier to read and understand. In this case, 'e' could be replaced with 'error'.
Create Issue

    .catch((error) => {
+      console.error(error);
+      return { success: false, error: 'An error occurred while processing your request.' };
    });

server/endpoints/admin.js

It's a good practice to not expose the actual error message to the client. Instead, log the error message and send a generic error message to the client. This prevents potential attackers from gaining insights into the internal workings of your application.
Create Issue

    } catch (e) {
+      console.error(e);
+      response.status(500).json({ error: 'An error occurred while processing your request.' }).end();
-      response.sendStatus(500).end();
    }

It's a good practice to use meaningful variable names. This makes the code easier to read and understand. In this case, 'e' could be replaced with 'error'.
Create Issue

    } catch (error) {
+      console.error(error);
+      response.status(500).json({ error: 'An error occurred while processing your request.' }).end();
    }