gd-fetch

How to install, setup and use gd-fetch?

1 - Install: npm i gd-fetch or npm i gd-fetch@version.

Valid Versions: 0.0.1 • 0.0.2-BETA • 0.0.2 • 0.0.3-BETA • 0.0.3

2 - Require the library in your project:

const gd = require('gd-fetch');

3 - Make use of the functions available for the version of the library you use, offers.

Documentation

For old methods, goto gd-fetch

Additons:

• Fix to social (media) object of fetchUser.

• Update to diffString.

diffString - Now takes 3 parameters

• diff (read old docs)

• type (read old docs)

• dtype - Integer -1 to 6.

Providing -1 or 0 will make it just say Demon.

2 is Easy Demon, 3 is Medium Demon, 4 is Hard Demon, 5 is Insane Demon, 6 is Extreme Demon.

Providing higher or lower values than specified above will result in a rejection.

External sources and own sources

• String | MDN

• Object | MDN

• Number | MDN

• Promise | MDN

• Function | MDN

Another source you may refer to, can be w3schools.

Error codes (registering accounts or common errors in general)

0 - Error response from this library itself, can be caused by unknown error or invalid form data. GENERAL

-1 - Server-sided (unknown), can be caused if the server denies the action or server returning nothing. GENERAL

-2 - Username taken, caused by username you try to use for your account is alredy in use. ACCOUNT

-4 - Invalid username, caused by username being invalid e.g too long or invalid characters such as dots, paranthesis etc. ACCOUNT

-6 - Invalid email / email alredy in use ( / Banned mail), caused my using an email alredy or not meeting certain criterias in use (or one banned from the GD servers). ACCOUNT

Developers

Rageous0

• Website

• Github

• npm

• Twitter

zCri

• Github

gd-fetch links

• gd-fetch

• Github repo

• gd-fetch docs 0.0.1

• gd-fetch docs 0.0.2-BETA

• gd-fetch docs 0.0.2

• gd-fetch docs 0.0.3-BETA

• gd-fetch docs 0.0.3

Each versions docs just includes the features that got in that specific version!

Up to date since?

The README was last updated and written to the 2nd of February (2019).

Also if you have concerns please report it as an issue on the github repo, and we'll try to figure it out!