minecraft-data (PR submitted)
minecraft-protocol (Maybe? Types for the objects to client.write would be nice but I don't know if it's possible based solely on the string)
prismarine-chunk (Should be easy, as should the following)
prismarine-entity
prismarine-item
prismarine-world
prismarine-windows
prismarine-provider-anvil

Then we have the non-prismarine stuff, which we made need external typings for

vec3
random-seed
moment has its own type defs
emit-then
event-promise (there's this which looks much more, dare I say it, promising than our current library. It has types already and an actual README and such, so maybe we should switch?)
diamond-square (Owned by rom, very basic API, should be fine)
flatmap is used in one test, I doubt we need it for this
mkdirp is also used in one place
node-uuid is deprecated, apparently we should be using uuid which has types
range, similar to flatmap, only used in one spot. Maybe it might be worth creating basic lib functions for these things, since I don't think we should make people install packages for such basic function (also, range could just be done with [...Array(100)].map(i => i)
spiralloop is mine, but again, it's only 50 lines, does it deserve its own package? Especially since it's used in one place.
request
request-promise

We could add the devDependencies but I think this is enough for now 😉

Of course, we don't have to do all of these, just some stuff to think about. I can at least try to do the prismarine ones.

Flow/TypeScript #323

Description