You can run the build script with npm run build. Parses the external data to match our schema and returns it to the build script. Here we also save JSON, image and cache data.įetches all external data and returns it to the parser.
Build Tools ( build-essentials on linux should be enough, on windows run npm i -g windows-build-tools)Īll relevant scripts are found in /build/ with. We're always happy to see contributions to this project, so here's some basic setup information Since there are so many images, and we can't publish them on npm due to the size, we've set up a CDN to get you images at $ that provides a linkable resource for you. You can find every item's image name stored in item.imageName. You can find all automatically compiled data in /data/json. Modifications for weapons, warframes, archwings, etc. Useful if you don't wanna load lots and lots of MB of data into memory. items paramĪllows you to add your own items before our gathered ones.Īrray of item categories to retrieve. In this example, items is an Array with all items. 
You can also rest assured that this repository will be maintained for as longĪs Warframe stays alive, as it is has been built to provide all item data for NexusHub.Ĭonst Items = require ( 'warframe-items' ) const items = new Items ( options.
Unique ingame name - (/Lotus/Weapons/Tenno/.) - Especially useful when working with worldStateĪnd tons more item specific data. We also make sure to include every other data aspect Why use this instead of any other scraper?īecause this gives you literally every item in Warframe, many of which can't evenīe found on the wikia. Updated on every new release, drop rate change or image change. Item in Warframe based on the game's own data. 
The aim of this library is to create a complete collection of data for every Fetches all items available on Warframe's mobile API endpoints while alsoĪdding images, drop rates, patch logs and related rivens.
0 kommentar(er)
