Jest is a testing framework with a focus on simplicity. We will have continuous testing that runs whenever we modify and save files in our project. We will also install a VS Code extension and configure it to automatically format-on-save other file formats (JSON, HTML, Markdown, YAML, etc.), too.
We will configure ESLint to apply Prettier styles as fixable linting rules and automatically style the code every time we save the code. It eliminates all custom styling by parsing the code to an abstract syntax tree (AST) and then re-printing it according to its own consistent rules. It takes maximum line length into account, causing it to reflow single-line statements into multi-line statements if they get too long, making code more readable.
Prettier is an opinionated code formatter that understands JavaScript code formatting conventions. We will have automatic style-on-save behavior. The TypeScript language service in VS Code provides support for inferring the types in JavaScript files and reporting any type errors it detects, so we will enable that continuous linting feature, too. We will use a VS Code extension to integrate continuous static analysis into the source editor view, and we will configure VS Code to use ESLint to automatically fix everything it can, every time we save our code. We will configure ESLint to use rules from the popular Airbnb JavaScript Style Guide so that our code follows common standards. It can even fix your code for you (sometimes). For instance, it can detect if you use variables that haven’t been defined. We will have continuous linting and automatic fix-on-save behavior.ĮSLint is a highly configurable static analyzer, able to report problems in your code before it runs. This feature is enabled by default and alone is a great reason to use VS Code for JavaScript development. It includes an IntelliSense feature based on the TypeScript language service, which provides smart completions and parameter info for JavaScript. VS Code is a free, open-source code editor. We will have intelligent code completion. While current versions of Node have experimental support for native modules, by using Sucrase and restricting ourselves to mainstream ES6 syntax in our code, we can target any version of Node all the way back to LTS version 8. We will use the Sucrase compiler to transform our code before running it with Node so that we can write native ES6 modules, instead of traditional Node CommonJS modules. We will have modern JavaScript features, like arrow functions, import/export, async/await, and object rest/spread properties.Īs of the latest LTS version 12, Node has near-complete support for everything in the ES2019 standard - except for native (ES6-style) modules. Before we begin the tutorial, let’s review our five primary goals.
0 kommentar(er)
