For example, trying to fetch someone's anime lists

const lists = await Anilist.lists.anime(USERNAME);

(node:10625) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'activities' of undefined
    at Utilities.send (/.../node_modules/anilist-node/lib/fetcher.js:127:28)

https://github.com/Butterstroke/AniList-Node/blob/master/lib/fetcher.js#L127-L129

An easy fix would be to check if the Page property is defined before trying to access the deeper properties

if (json.data.Page && json.data.Page.activities) { ... }

Description

When generating the JSDoc documentation, instead of AniList.Lists as the HTML file name, it uses Anilist.Lists.

Release 1.9.1 shipped with this mistake but running the docs script after release generated the correct file name.

Steps to Reproduce

1. Run the NPM docs script
2. Open the newly generated documentation
3. Click on Lists class in the navigation bar
4. Fail to load Lists page

Environment
Node.js Version: 12.22.6
AniList-Node Version: 1.9.1

Screenshots

Additional context

Are there any plans on providing Mutation wrappings according to https://anilist.gitbook.io/anilist-apiv2-docs/overview/graphql/mutations ?

I want to use this package with my TypeScript project but I am not shown any method as it should be in TypeScript.

Tested package version: 1.2.2
Tested Node version: Node 12
Affected areas: Staff function

Staff function returns null if you search for a staff member by their ID and not by their name.

As documented here there is rate limiting in place. While it is fairly generous currently at 90 rpm, I'm not sure if there's any way to use this from the node wrapper.

Would it be possible to either:

1. Expose the useful headers from the library:

Retry-After: 30
X-RateLimit-Limit: 90
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1502035959

2. Automatically handle it inside the library, by holding off on sending/resolving the promise response until the call has been made without exceeding the rate limit.

Would this be in scope for the library or do you have any advice for not exceeding the rate limit? Thanks!

Description

Need I say more?

Steps to Reproduce

As seen in the screenshot above, hover over the code to see a number type, run the code however and you will see an object.

Environment
Node.js Version: 18.12.1
AniList-Node Version: 1.13.0

Screenshots

Already included above.

Additional context

A discord conversation starting here in the Discord support server

Description
In lib/fetcher I found a possible issue. Read the following code.

https://github.com/Butterstroke/AniList-Node/blob/68c8006331ac304fbc11eddb4e64f4b4bccf08dd/lib/fetcher.js#L129-L137

The first statement returns errors if there are any, this means that if there are no errors it will continue to the next statement.
We now know that json.errors is a falsy value because otherwise it would have already returned.

However, in the second statement, if (json.date === null), we are accessing json.errors anyway.

TL;DR: Accesing json.errors after we now it's a falsy value

Environment
AniList-Node Version: 1.8.1

Additional context
Code in: lib/fetcher, lines 129 - 137

Users are currently restricted by the first page of the related entries to many of the methods right now. The first page has 25 entries, as per AniList's limit, but it is possible to query for more entries. Users should have an optional parameter in methods to get the next 25+ entries if they wish.

For example:

One Piece has 53 related entries right now but with media.anime() it is only possible to get 25 of those entries.

Because of the way the query is setup,

relations { nodes { id title { english native romaji userPreferred } type } }

will only ever return 25 entries.

While a change like this,

relations (page: x) { nodes { id title { english native romaji userPreferred } type } }

would allow users to query for other entries that would not be listed on other pages.

Each entry that grabs related entries (ie: characters & media) is a connection so those changes should work fine for the GraphQL queries.

Edit: Updated with more explanation and example.

Is it possible that u can use name not ID?

Description
I'm trying to make a discord bot with AniList API. However, when i'm trying to execute command of find e.g. user (this problem are occured on anime and manga too) it's returns a Bad Request HTTP error

Environment
Node.js Version: 20.9.0
AniList-Node Version: 1.14.0

Screenshots

Allow users to have a method to update their anime lists. Something to note is that anime queries don't allow names and must use their AniList IDs. Searching by names is also not as accurate as using an ID. So users should only be able to update if they have the ID of the anime in question.

Allow users to have a method to update their manga lists. Something to note is that manga queries don't allow names and must use their AniList IDs. Searching by names is also not as accurate as using an ID. So users should only be able to update if they have the ID of the manga in question.

Tested package version: 1.2.2
Tested Node version: Node 8 & Node 12
Affected areas: All searching capabilities

When using the search function, AniList currently returns an empty page.

Description
Use of arguments is currently not possible with default code.

Steps to Reproduce

1. Load the module into your project
2. Attempt to use the example code like this

const anilist = require('anilist-node');
const Anilist = new anilist();

Anilist.media.anime(**args[0]**).then(data => {
    console.log(data);
});

3. Receive the "Term provided is not a number!" error

Environment
Node.js Version: 14.15.4
AniList-Node Version: 1.7.0

Screenshots

Additional context
Commented out line 25 in this file
https://github.com/Butterstroke/AniList-Node/blob/master/lib/media.js
Arguments were able to pass through, and the correct data was grabbed.

While the addition of this line helps make sure the correct string is passed, it checks the code before the actual argument and kills the process. Might want to add some exception for args[...]

https://github.com/Butterstroke/AniList-Node/blob/68c8006331ac304fbc11eddb4e64f4b4bccf08dd/lib/fetcher.js#L71-L73
https://github.com/Butterstroke/AniList-Node/blob/68c8006331ac304fbc11eddb4e64f4b4bccf08dd/lib/fetcher.js#L28-L50

Is there any point in using await on edgeRemove? It doesn't return a promise. If the awaiting of those functions is removed, function formatMedia for example doesn't have to be executed asynchronous anymore.

Unless there is a thought behind this, in that case I would like to know the explanation 😄

Originally posted by @Exhabition in #28 (comment)

Hmm... I believe the thought was to ensure the object was edited before it was returned. I'm trying to think if edgeRemove was always synchronous or not but I can't say for sure since it's been around forever. Might be worth a look to see if synchronous is just as good for it.

Originally posted by @Butterstroke in #28 (comment)

Does this have like a command to view your friends Activity. Like what that person watched/read today.

Description

When using moduleResolution: node16 or nodenext in tsconfig.json, building with a call to the module causes the following error :

$ tsc
services/animeList.ts:12:21 - error TS2351: This expression is not constructable.
  Type 'typeof import("C:/xxx/karaokemugen-server/node_modules/anilist-node/lib/types/index")' has no construct signatures.

12 const anilist = new Anilist();
                       ~~~~~~~

Steps to Reproduce

1. Create a new typescript project with moduleResolution: node16
2. Try to spawn a new instance of Anilist in your code as described in the README.

Environment
Node.js Version: 18.12.1 (tyepscript version 5.0.2)
AniList-Node Version: 1.13.1

Thanks for looking into this! This would help a lot with a project I'm trying to keep up-to-date.