Nathan Totten

@bradwestfall @luisllanes_ @cursor_ai I'm sure they have good reason why Cursor 2 is on an old VSCode extension API, but its going to end up causing a lot of problems like this if they don't catch up soon. We can probably solve the issue for this extension, but needs to be on their side ASAP.

@ntotten @luisllanes_ @cursor_ai Would love to see @cursor_ai accommodate instead of the other way around.

Having prettier, cursor, vscode issues. Version 12 of the plugin came out hours ago and prettier stopped working for me. The only fix was downgrading to 11 and telling cursor not to do auto updates. The gear icon allows you to install specific version

@bradwestfall @bentsignal @luisllanes_ @cursor_ai @leerob **try to publish a new version soon.** - apparently edits on here are a paid feature. :)

@bradwestfall @bentsignal @luisllanes_ @cursor_ai @leerob It was going to be way too much work and negatively impact too many people so I gave up on that effort. The VSCode marketplace is going to redirect the "prettier.prettier-vscode" extension to the "old" location. Not sure if OpenVSX supports that. I'll to to publish a new version.

@bradwestfall @luisllanes_ @cursor_ai @mntruell IMO, Cursor should have a supported way to run CI tests for extension authors if they’re going to be different from VSCode’s extension API. From what I can tell this isn’t possible today.

@bradwestfall @luisllanes_ @cursor_ai Maybe @mntruell can find some folks who can help out. I’m open to publishing a CJS version to OpenVSX as I’d imagine the vast majority of installs from there are from cursor, but it will take a bit of work and testing.

A lot of work goes into launching any product @zuplo, but we wanted a little extra for our AI Gateway, here's a peek behind the scenes...

@JAdiaheno @github @npmjs Ha, yeah. We are doing the same.

@ntotten @github @npmjs We spammed the retry button, and it finally passed. But this is a disputed GitHub actions bill for sure.

A bunch of ECONNRESET all over my npm install in my GitHub actions. @github @npmjs all good?

Follow me on Bluesky: bsky.app/profile/ntotte…

I just want to listen to music @Sonos. It’s been over a year since things worked reliably. 👎

Your current API experience will likely break down at an enterprise scale. Here's why: - 👥 Your account-sharing system is too rigid - 📊 Your reporting isn't granular enough - 🔑 You only issue 1 API key Learn how Subaccounts can solve these issues: hubs.li/Q02X_T4G0

How much are you spending on your API Integration Platform? Whether it's @boomi or @MuleSoft - these platforms can get expensive ($100K+/year), especially when you can build in-house quickly and affordably. Learn how here: hubs.li/Q02XNx9X0

It seems like every month, a new Python web framework is launched - with better performance or a cleaner syntax. Most of these frameworks usually forget about OpenAPI. We couldn't find a list of OpenAPI-supporting Python frameworks, so we made our own: hubs.li/Q02WXNtc0

The technical steps to deprecating a Node REST API are simple, but you might end up fighting with your framework if done incorrectly. Here's our latest guide to deprecating your Node JS REST API (with examples in 6 different frameworks): hubs.li/Q02WXK250