Monorepo initialization & new APIs

[PalmDevs]

⚠️ Issues with adding new APIs

As things progress, Revenge will have to add new features and APIs. Adding these changes directly to the window.vendetta API will affect other forks, eg. Bunny. We've discussed this internally and the solution was to add new APIs into window.revenge object which plugin developers can check for and use responsibly.

❓ Why initialize a monorepo?

Using a monorepo allows for better project structure and management, as well as helping separate parts of code which makes it easier to work with.

🛠️ Implementation

This will be the project's structure:

📂 packages
|_ 🟦 vendetta
|  |_ 📂 src
|     |_ 📘 index.ts
|     |_ (...)
|_ 🧰 components
|_ 🔨 utils
|_ 💉 register
|  |_ 📂 src
|     |_ 📘 index.ts
|_ (...)

To add window.revenge, we can call the @revenge-mod/register package:

// packages/vendetta/src/index.ts

// ...
import '@revenge-mod/register';
// ...

export default async () => {
  // ...
};

In the @revenge-mod/register package, the window.revenge API is assigned:

// packages/register/src/index.ts

import components from '@revenge-mod/components';
import utils from '@revenge-mod/utils';
// ...

window.revenge = {
  components,
  utils,
  // ...
};