Skip to content
This repository has been archived by the owner on Aug 26, 2022. It is now read-only.

RedwoodJS and VSCode

Nikolaj Ivancic edited this page Mar 20, 2021 · 11 revisions

Why VSCode

It is easier to state the development solutions we do not plan to cover:

  • using the Windows Notepad and Windows CMD.EXE, which is the minimally needed JavaScript development setup.
  • using Cygwin (Get that Linux feeling - on Windows).
  • using coLinux.
  • using Windows Subsystem for Linux.
  • many other ... (to be defined)

Instead of all these (some insufficiently sophisticated, other difficult to install, and too difficult to support (by Redwood support team), we will strongly endorse the use of the Visual Studio Code (aka VSCode) editor and the set of related tools. By doing this, the developer "unloads" all platform dependent issues in the process of developing and deploying Redwood applications to Microsoft's platform-independent layer, present in VSCode

Note: this document will contain the Redwood list of recommended extensions) which currently include the Redwood specific set shown on this screenshot below:


VSCode extensions

Meta:

Here comes the detailed list of Top Visual Studio Code Extensions: 50 Powerful Tools, like these presented below (as an example of the complete list):



Feature Description
image Intellisense - Go beyond syntax highlighting and autocomplete with IntelliSense, which provides smart completions based on variable types, function definitions, and imported modules.
image Visual Git built in - Working with Git and other SCM providers has never been easier. Review diffs, stage files, and make commits right from the editor. Push and pull from any hosted SCM service.
image Deploy and host your Redwood (JamStack application with simple drag and drop commands or, using console SSH commands

VSCode settings

Meta:

Here comes the list of Visual Studio Code settings that are relevant for Redwood application developers. The example below points to the discussion about the Windows console settings (note that the console could be a tool independent of VSCode, as well as a part of it