Today we are releasing the public beta of the @stripe extension for @code, which brings Stripe inside your editor. Let me give you some background on why we built this extension, what it does, and where we are going with our developer tools.
https://stripe.com/docs/stripe-vscode
A thread
https://stripe.com/docs/stripe-vscode
A thread

By bringing Stripe inside code editors, we move Stripe-specific information inside the context where developers already are when they build. We believe this will reduce context switching, reduce friction, and make it faster to integrate, build, and test with Stripe.
We decided to start with VS Code, one of the most popular code editors, and build an extension that would bring in a range of common workflows through a new Stripe panel in the activity bar and a set of custom commands.
Let me walk you through the features:
Let me walk you through the features:




So we'll now analyze and lint your code and show you warnings if you leave a hardcoded API key behind by mistake.



Code snippets brings code examples from our docs into the editor, so you have less code to write and everything in one place.


We are just starting to scratch the surface of what it means to bring Stripe closer to your source code and inside your editor.
What would you like to see in your favorite developer tool? What would improve your developer experience with Stripe?
What would you like to see in your favorite developer tool? What would improve your developer experience with Stripe?