My extension interacts with the ROBLOX API and I assumed I was going to need to make every function one by one… Until I remembered about this library I heard of called “Noblox.JS”
Nice now I don’t have to waste my time making boilerplate code
Oh wait what’s this? It’s for Node.JS?
Oh well, time to search for better alternatives
Oh… Every SINGULAR ROBLOX API wrapper made in Javascript is made for Node.JS?
Oh noes! Oh woe! Alas, What shall I do now? What actions must I partake in to mend this horrible mishap I have crossed paths with? How mockingly my niggardly peers must think of me for acting so perplexed and bewildered by this miniscule, niggly struggle - quite the epitome of duncish behaviour to say the least. How I have endeavored with every last bit of strength. How I have attempted to push forward with the persistance I had left. Unfortunately, to my dismay, quickly have I recognized the fire that has been set ablaze has been put out. Looking in my wearied eyes, you could see the despair. I knew from the bottom of my heart, I couldn’t… I musn’t continue. Going even further would take a toll on my mind and body. I sense there is somebody more worthy out there brave enough to endure the difficulties of this task. Oh, how I yearn for the guidance and salvation of my future merciful saviour, to heal my sorrowful, saddened soul.
This may be the best way to do this actually. It gives you total control over how you interact with the APIs and freedom to modify your calls in case Roblox changes something in an upcoming update(I have seen them mess with the urls way too many times). If you feel writing API call code starts to get repetitive you can make helper functions so you write less(for example most GET requests are similar to each other, same goes for POST requests).
not sure what you actually mean, but i meant that the op can modify their own extension’s manifest, and anyone who installs the extension on chrome-based browsers will be able to bypass the cors for the api hostnames