Cleanup unnecessary nested promises in services. about digitalocean-js HOT 4 CLOSED

Looping back on this, I finally completed a fairly major overhaul to the project structure to convert it to an NX workspace instead of the custom typescript seed project I originally used. I've also begun the process of writing some tests for the library. As part of that project overhaul, since I was changing everything anyway, I also went through and unwrapped the promises like you requested. Great suggestion, thanks! Closed in #49.

from digitalocean-js.

Hey @tracker1 sorry for the delay in going through this, it's been a busy few months for me. Love to see your desire to use this project in Deno! I haven't had a chance to look through your changes, so give me a little time to go through it and see whether I'm interested in merging those changes back in. I'm in the process of migrating my whole library setup to use NX instead of the current setup that is using a lot of old technologies, so that's going to move some stuff around. Nothing majorly changed to the code itself, but it may be worth waiting until that change is merged.

Again, love the enthusiasm for the project! I'll get back to you as soon as I can!

from digitalocean-js.

@johnbwoodruff understandable... also have a todo list a mile long for myself on top of the day job. Will keep an eye out to more replies in this thread.

For now, I was able to get the library working for my immediate needs, which was the main thing at least for my own use case. Kind of wild how much the JS/TS ecosystem has shifted over time... It's almost another dark ages trying to keep what goes into the browser, deno, node etc all working in something resembling reusable code. I'm really liking Deno a lot more than Node in so many ways, but the rich npm packages is something that's not the easiest thing to get over, and some of the bridge options aren't great for modern(ish) packages.

from digitalocean-js.

@johnbwoodruff ping

from digitalocean-js.