What's New (Page 2 of 2)
VS Code now provides two additional settings that allow you to automatically start Quokka when a file is opened. The
quokka.automaticStartRegex setting allows you to configure Quokka to start automatically when your file matches a regular expression. The
quokka.automaticRestart setting can be set to
true (default is
false) to automatically start Quokka on a file if it was running when the file was last closed.
Quokka ‘Pro’ now allows users to change the behavior of Quokka to use
to automatically show the runtime value for every line of code. This behavior can
be changed after starting Quokka using the Toggle Auto Log command. By default, this
behavior is disabled but the default may be changed using the
autoLog configuration setting.
Previously Quokka would log an infinite number of values for
repeated code (e.g. within a loop). For a large number of iteration,
this could lead to slow Quokka execution and out of memory exceptions.
Quokka now limits the default number of values output for repeated code to
this can be changed with a Quokka setting.
Previously Quokka would ignore any errors in your global
.quokka JSON file and attempt to execute your Quokka file with
default settings. Quokka will now halt execution and report the error if it cannot
correctly process/merge your settings files.
scratchAutoStart with a value of false.
VS Code now provides a list of all recently launched Quokka files (both physical and scratch files) which may be viewed by using the
View Recent Files command. This view displays the contents of the files (search with Ctrl/Cmd + F), the date the file was last run, and provides a number of actions. Read more in our docs.
We made significant improvements to Show Value detection when using
Show Value, and
Copy Value. This update enables fuzzy token selection instead of previously having to select an exact token to output. In addition to being able to show values for additional syntax constructs, the feature also now has better support for code transpiled with TypeScript and Babel.
Live Values are now
sticky which means that they survive your file changes
while being updated as you type. Values may also be hidden in VS Code and JetBrains
Escape to clear a value or
Escape Escape to clear all values in
Our first big feature of 2021 is expected to be a game changer for many of our users. The CPU Profiler allows you to quickly and easily get the CPU Profile of your code to analyze its runtime performance. No configuration is required, one simple click and you will see the CPU profile.
While not directly related to the Wallaby product, the Wallaby team created and released the Dingo VS Code extension that makes it easier to download, install and open git repos and the source code for npm packages, right from the comfort of your editor. The source code is available on GitHub under an MIT license and the extension is free for everyone to use.