
Product
Introducing Custom Pull Request Alert Comment Headers
Socket now lets you customize pull request alert headers, helping security teams share clear guidance right in PRs to speed reviews and reduce back-and-forth.
@blizzard-api/wow
Advanced tools
A series of helpers to interact with the World of Warcraft Blizzard API
This package aims to make it easier for you to integrate with the Blizzard Battle.net API, specifically for World of Warcraft.
npm i @blizzard-api/core @blizzard-api/wow
You can get paths, namespaces, parameters and more for a specific endpoint by calling it from the wow
export.
import { wow } from "@blizzard-api/wow"
//or
import wow from "@blizzard-api/wow"
const achievement = wow.achievement(123);
^ { path: string, namespace?: string, parameters?: Record<string, never> }
If you don't want to use the exported wow object, you can also access the functions directly:
import { achievement } from "@blizzard-api/wow"
const achi = achievement(123);
^ { path: string, namespace?: string, parameters?: Record<string, never> }
If you need the response types, they are also exported with "Response" appended, so to get the response type from the above code, you can import it like this:
import type { AchievementResponse } from '@blizzard-api/wow';
If you simply want to use the existing object, you can use the helper, ExtractResourceType
, from @blizzard-api/core
like so:
import type { ExtractResourceType } from "@blizzard-api/core";
import { wow } from "@blizzard-api/wow"
const achievement = wow.achievement(123);
^ { path: string, namespace?: string, parameters?: Record<string, never> }
type AchievementResponse = ExtractResourceType<typeof achievement>;
This package is specifically for World of Warcraft (retail or modern), and as such, the endpoints and responses are different from the classic variants. If you are looking for the classic version of World of Warcraft, you should use @blizzard-api/classic-wow
instead.
The types are manually created from using the Blizzard API documentation, and are as accurate as possible with smoke testing each endpoint. However, no-one is perfect so there is likely to be some discrepancies. If you encounter any issues with the types from this package, please open an issue or a pull request.
While this package is made to function on it's own, it performs even better when combined with @blizzard-api/client
where you can easily request data combining the two libraries.
import { createBlizzardApiClient } from '@blizzard-api/client';
import { wow } from '@blizzard-api/wow';
const client = await createBlizzardApiClient({
key: 'environment.blizzardClientId',
secret: 'environment.blizzardClientSecret',
origin: 'eu',
});
//Response will automatically be typed with the appropriate values
const response = await client.sendRequest(wow.commodities());
console.log(response);
^ typeof AuctionHouseCommoditiesResponse
FAQs
A series of helpers to interact with the World of Warcraft Blizzard API
The npm package @blizzard-api/wow receives a total of 41 weekly downloads. As such, @blizzard-api/wow popularity was classified as not popular.
We found that @blizzard-api/wow demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket now lets you customize pull request alert headers, helping security teams share clear guidance right in PRs to speed reviews and reduce back-and-forth.
Product
Socket's Rust support is moving to Beta: all users can scan Cargo projects and generate SBOMs, including Cargo.toml-only crates, with Rust-aware supply chain checks.
Product
Socket Fix 2.0 brings targeted CVE remediation, smarter upgrade planning, and broader ecosystem support to help developers get to zero alerts.