Today, 3 months ago, we had the first WarEraProjects/API client release!

Here is a quick history on the project!

v0.1.0 💚 - Initial Project Release

This was the first commit, containing the necessary code to communicate with api2.warera.io, a Rate Limiter, and allowing for both input and response type handling.

v0.1.1 🔍 - ReadMe

Improved ReadMe.md docs

v0.1.2 📚 - Auto-Pagination

This is the first big update of the project.
The Auto-Pagination allows the developer to quickly iterate through "Pages" when calling an endpoint using a cursor

With the new loop strategy, you could immediately use the incoming data as the next was being fetched.
From this point on, the data fetching started improving drastically, as you could call fetches without waiting for it to be resolved.

v0.1.3 ❌ - Reduce Options

The goal of the package is to do less work, meaning that configuration should also be less.
This update changed options to be optional, replacing expected values as defaults.
At this stage, one would only need to provide an API key to get started.

v0.1.4 🚨 - Reduce Input Parameters

In some cases, the client would not work, if you did not provide an empty object.
This was fixed.

v0.1.5 🍵 - Buy me a Coffee button added

This button has never been used, it is what it is.

v0.2.0 📲 - Change GET to POST

This update improved the communication speeds drastically with the server.
Instead of sending a long GET request to the server, you can now send a smaller URL with a larger Payload.
The client does a check for 16000 characters in the URL, before splitting it up into different requests, the responses are combined later on and returned as one object.
Benchmark tests were added.
The client received a batch logger, allowing the developer to debug the batch requests.

v0.2.1 💻 - Make it work, on the front-end

The application used a dependency which could only be run on a server.
Update function names for easier use.
Benchmark updated: Instead of waiting for a promise to complete, continue the loop.

v0.2.2 🤖 - Updated Missing Response Types and Endpoints

Added Missing Endpoints.
Created standard for future missing endpoints.

v0.3.0 ⚠️ - Fallbacks & New Endpoints Updates

Added retry fallback support for batched tRPC requests, including configurable retry behavior for dropped connections and transient HTTP failures. Expands endpoint coverage across generated API types, fallback collection workflows, and custom endpoint typings, adding support for item offers, user lookup, battle orders/loot summaries, inventory equipment, mercenary auctions, donations, elections, MU members, trading orders, work stats, wage stats, party pagination, and company production bonuses.

v0.3.1 🏃‍♂️‍➡️ - Batch Limit Imposed

The server imposed a new Batch Limit, where it can only go up to 50 requests per batch.
This patch resolves that issue

v0.3.2 ⚔️ - Added Tournament Endpoints.

What is next?

At the start of this week, I asked for suggestions. There were some good suggestions, so here is the plan:

• Alternative Rate Limit Setups

• Allow Requests to be Aborted

• Integrate with the Gateway for Caching

• Manage a Client Singleton to be used anywhere in your project.

• Generate Documentation for Public Use

• Allow Client to return a Status Code based on Server Availability

• Fast Fetching Algorithm for Cursor-based endpoints.

Feel Free to checkout the Project yourself!

GitHub - NPM

Chat with me on Discord