![]() This is something I've seen asked for several times when developers are moving over to VS Code - the VS Code key bindings are key bindings, just like any other text editor has its key bindings. Definitely check it out if you'd like to go a bit deeper with the subject. If you're interested in the Docker extension for VS Code, we recently did a webinar with Jonathan Carter of Microsoft going over the full development lifecycle of building and deploying Node.js apps with Docker and orchestrating them with Kubernetes. There's a lot to digest with Docker - I'm still getting up to speed myself - but this extension is a super helpful tool to help you speed up and automate your workflows around Docker. It has a host of features, including being able to generate a boilerplate Dockerfile for your Node.js app, adding in syntax highlighting for Docker-related filetypes, adds linting for Dockerfiles, and a host of other small but useful features. The Docker extension is a powerful utility for kicking off containzerization with Docker directly from within VS Code. Ecosystem Extensions and Utilities to Start Using with VS Code Docker I like this, as it provides a simple feedback mechanism to personally monitor and tone things back if I need to. If you're implementing something in a crazy complex way, Code Metrics will surface that you may be taking a bit too complex of an approach. Put simply, it analyzes your JavaScript (and TypeScript, too) and informs you on the interpreted complexity of it. Code MetricsĬode Metrics is a pretty awesome extension for self-monitoring. This extension allows takes advantage of the Chrome Inspector Protocol to allow access to debugging from within VS Code - I really love this, as it allows me to have the debugger info in my text editor and work on everything from a single location. The Debugger for Chrome extension is a really powerful tool, and is honestly one of my favorites. If you're not sure why you should be using a linter in your projects, or just not convinced that you need one, I wrote an article on how ESLint can help streamline your JavaScript workflow a while ago - you should take a read, if you'd like to get started. ![]() So, installing the most popular ESLint extension for VS Code is something that will help you get settled with your current config or smooth out the barrier to entry with linting. ESLintĮSLint is, at this point, the linter that most Node.js developers use - even if you use something like StandardJS, you're just using a standardized ESLint config. The extension is dead simple, but provides a nice quality of life improvement when in development. ![]() ![]() The npm InteliSense extension is a small utility to enable autocompletion of module names in require statements using the VS Code IntelliSense feature. Node.js Extensions to Start Using with VS Code npm IntelliSense Today, I wanted to highlight some extensions and tools and help you get up and running with VS Code as the perfect text editor for Node.js. I've personally tweaked VS Code to be streamlined to my taste for writing apps in Node.js, and wanted to share some of the Node.js tooling (outside of N|Solid and Certified Modules) that I use. I personally use VS Code to write both code and prose. Text editors can be as in-depth or as simple as you want them to be. As developers, there's one type of tool that we all use to express our intents into a langauge that systems can interpret and act on: the text editor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |