Urgent.News

What's breaking now, across thousands of outlets.

Tech

Line-anchored output and the filter chips

JSLab feature notes: one docs page, explained. Today: The output panel . JSLab is a JavaScript & TypeScript scratchpad for macOS. You type, it runs, and the output panel fills up. This note covers the two things that make that panel readable: every row knows its line, and four chips filter what you see. Every row knows its line Each result, log and error appears as a row tagged with the line that…

JSLab is a JavaScript and TypeScript development environment for macOS. When you type code and run it, the output panel fills with results, logs, and errors. Each entry is a row tagged with the line of code that produced it, allowing you to quickly navigate between the editor and the output.

Hovering over a row highlights its corresponding line in the editor, and clicking a row's line number jumps the cursor to that line. When you re-run the code, output rows with updated values flash for a moment, giving you an instant sense of how your changes impacted the results.

Above the output panel, there are four filter chips: All, Results, Logs, and Errors. Each chip displays a live count of the respective entries, and the counts remain visible even when they're zero. Results include values from Auto Log and magic comments, Logs consist of console.log, console.info, and console.warn, while Errors encompass thrown errors, stderr, and failed console.assert.

For example, if an error is thrown during a run, it appears tagged with its line number and corresponding stack frames. The filter chips show All 2, Results 1, Logs 0, Errors 1, indicating the number of entries in each category.

These filter chips are also accessible through commands in the command palette (⇧⌘P). Additionally, you can copy all entries by right-clicking in the panel and selecting "Copy All," which is useful for pasting the filtered output into an issue or another document.

Output highlighting and line numbers are customizable in Settings → Appearance. By default, JSLab colors values by type and shows the source line number beside each row. The software launches on November 15, with a full documentation page available at https://js-lab.app/docs/output.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Implementing 2026 Seller Compliance Practices for Retrying Failed Email API Calls

TL;DR: Retry a failed email API call only when the response is plausibly transient, use capped exponential backoff with jitter, and write an immutable attempt record before each sleep.

  • Implement capping mechanism for exponential backoff with jitter
  • Record attempt details for B2B marketplace orders
  • Distinguish between API acceptance and downstream delivery

Custom fields on the WooCommerce Checkout block: why your old snippet does nothing

If you added a checkout field with woocommerce_checkout_fields or printed one on woocommerce_after_order_notes , and it's simply not there on a newer store, the store is probably using the Checkout…

  • WooCommerce Checkout block introduced in 8.3
  • woocommercecheckoutfields only partially supported
  • Additional Checkout Fields API introduced in 8.9

Java Virtual Threads vs Kotlin Coroutines: Suspension Models and the Shifting Bottleneck

The usage and internals of Java virtual threads and Kotlin coroutines are already widely covered. Rather than explaining each technology separately, this post compares how their different ways of…

  • Java virtual threads save stack for suspension, OS threads resume
  • Kotlin coroutines save local variables and label in Continuation object
  • Both shift resource bottleneck to less visible location

More from Monday 2 November →