# VS Code Extensions recommendations? **URL:** \ **Category:** Development\ **Created:** [March 25, 2021, 9:30pm UTC](https://meta.discourse.org/t/vs-code-extensions-recommendations/184456 "2021-03-25T21:30:17Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\ **Post date:** [March 25, 2021, 9:30pm UTC](https://meta.discourse.org/t/vs-code-extensions-recommendations/184456/1 "2021-03-25T21:30:18Z")
I’m an aged use of Emacs. I’ve been trying VS Code for a while. (Surprise–it’s no easier to configure this infinitely extensible editor than it was emacs. I’ve not given up, and it’s really good for a few things, but I’m not even as much of a convert as I’d have hoped). So, does someone have a configuration that makes Rubocop, eslint, and prettier happy? It’s maddening to not be able to see that stuff until Travis complains and then copy-paste those commands (which should be in bash history by now) to figure out if stuff is wrong. Can’t I just make it format stuff on save, and warn loudly if it’s not auto-correctable?L If someone has this working in a way that’s beautiful, I’d love to know what set of plugins you’re using. But maybe I’ll go see about getting emacs to do this and the couple things I really like (the best so far being shift-control-f to grep a whole sub-directory tree. --- _[View the full topic](https://meta.discourse.org/t/vs-code-extensions-recommendations/184456)._