Release 0.5.0 (2021-10-12) · kyle-wannacott/blazing-releases

Beta release.

Various new errors (implemented by Himanshu).
quick-lint-js.config now supports the literally-anything global
group. Use this option to disable all
use-of-undeclared-variable warnings.
If quick-lint-js crashes, it will link to a page to report
crashes.
VS Code: The plugin now works on Windows on ARM (64-bit).
VS Code: The plugin now works on Linux on ARM (32-bit and 64-bit).
The CLI and LSP server now compile on FreeBSD (amd64). However, we don't
provide FreeBSD pre-built executables.
Neovim: nvim-lspconfig is now supported by quick-lint-js' plugin (implemented
by tiagovla).
VS Code: Contributors can now enable performance
tracing
(implemented by Jimmy Qiu).

LSP, VS Code: Filesystem change watching failures no longer crash. These
failures can happen on Windows for directories on network shares, for example.
LSP: Unknown messages no longer crash the LSP server. This makes the LSP
server compatible with more clients, such as Neovim's built-in client.
break await and break yield no longer incorrectly reports errors (fixed by
Himanshu).
for (var x = ++y in []) {} now parses correctly as valid JavaScript.
Vim: The plugin no longer crashes if a filename contains a newline character
(or certain other control characters).
LSP, VS Code: Config file changes are now recognized properly if any path
component contains a symbolic link (Linux and macOS).
quick-lint-js no longer warns about variables named __dirname,
__filename, exports, module, or require by default.
Parsing certain code patterns containing await/ no longer takes excessive
memory and time.
Various crashes on invalid code have been fixed.
LSP, VS Code: Some memory leaks have been fixed.
Arch Linux: building should no longer fail with "The install of the
quick-lint-js target requires changing an RPATH from the build tree".

Provide feedback