Start with a free account
Register once for two complete sample scripts on each scripting site. No card required. Annual membership is coming soon for the remaining library.
Create your free account or sign in →YOUR DAILY SUPPORT WORKBENCH
JavaScript Desk.
Find the task. Tailor the script. Keep your work.
27 distinct scripts · Search by task, subject or library · Node.js 22+
SEARCH → TAILOR → REVIEW → COPY
Find your next script.
TAILOR TO YOUR ENVIRONMENT
Choose a script
Official documentation ↗Review checks
Choose checks for the edited text. This page does not run your code.
UNDERSTAND WHAT YOU RUN
Modules, setup & testing.
Choose the right runtime
These support scripts run in Node.js, not the browser console. Save them as .mjs for ECMAScript module imports. Most use built-in Node modules; Azure SDK tasks require the packages listed in their requirements.
node --version node --check script.mjs # After review: node script.mjs
Modules and dependencies
node: imports identify built-in modules. Review package.json scripts before running npm commands. Prefer lockfiles and reviewed package versions for projects that need external dependencies.
import { readFile } from "node:fs/promises";
// Read-only dependency inventory in an existing project:
// npm ls --depth=0Asynchronous support tasks
await keeps network and file operations readable. Use explicit timeouts for remote requests and handle errors; a status response alone does not prove a service is healthy.
try {
const response = await fetch("https://example.com", {
signal: AbortSignal.timeout(5000)
});
console.log(response.status);
} catch (error) { console.error(error.message); }Validate and retain
node --check parses a file without running it. Text checks in this workbench are only pattern matching. Save modified code to the runbook and test on fixtures before operational use.
node --check script.mjs # Runbooks are browser-local, not cloud backups.
YOUR LOCAL WORKSPACE
Build a support runbook.
Saved in this browser only. Export before clearing browser data. Do not store credentials or confidential customer data.
BROWSE THE LIBRARY
JavaScript tasks, by subject.
Browse 27 distinct tasks. Two designated samples are available to registered free accounts; the remaining scripts are reserved for membership, which is coming soon.
Networking · 2 tasks
- Check an HTTPS health endpoint
Request one HTTPS endpoint with redirects disabled and a five-second timeout.
fetch · Node.js 22+ - Inspect DNS mail routing priorities
Read MX records and their routing priorities; diagnose DNS email delivery configuration.
node:dns/promises · Node.js 22+
Development · 2 tasks
- Inspect package.json scripts
List package lifecycle commands for manual review without running them.
node:fs/promises · Node.js 22+ - Find dependencies declared twice
Find package names present in both dependencies and devDependencies.
node:fs/promises · Node.js 22+
Data · 2 tasks
- Locate malformed JSON lines
Stream a JSONL export and show the line numbers that cannot be parsed.
node:readline · Node.js 22+ - Check URL inventory schemes
Classify URLs from a text file without contacting them; hide credentials and query strings.
node:readline / URL · Node.js 22+
Storage · 1 tasks
- Find stale files in one directory
Report files older than a chosen number of days; does not recurse or delete.
node:fs/promises · Node.js 22+
Diagnostics · 1 tasks
- Report Node runtime capabilities
Collect runtime, CPU count and memory information for a support ticket.
node:os · Node.js 22+
Files · 5 tasks
- Compare line sets in two files
Show added and removed unique lines, useful for simple exported inventories.
node:fs/promises · Node.js 22+ - Count directory entries
Count directory entries. Adapted from nodejs/examples with retained MIT licence.
node:fs/promises · Node.js 22+ - Detect a text file byte-order marker
Check the first four bytes for encoding markers without reading file contents into a report.
node:fs/promises · Node.js 22+ - Diagnose mixed line endings in a text export
Count Windows, Unix and lone-CR endings to diagnose import failures without printing or rewriting content.
node:fs/promises · Node.js 22+ - Find case collisions before a filesystem migration
Check a JSON array of file paths for case-insensitive NFC-normalised collisions before migration. This is a screening check, not full filesystem compatibility validation.
Unicode normalisation · Node.js 22+
Azure · 2 tasks
- Inventory resources in an Azure group
Inventory resources in an Azure group. Adapted from Azure-Samples/azure-sdk-for-js-samples with retained MIT licence.
@azure/identity / @azure/arm-resources · Node.js 22+ - Check Azure provider registration
Check Azure provider registration. Adapted from Azure-Samples/azure-sdk-for-js-samples with retained MIT licence.
@azure/identity / @azure/arm-resources · Node.js 22+
Security · 2 tasks
- Inspect local certificate validity dates
Inspect PEM certificate dates locally without connecting to a server.
node:crypto · Node.js 22+ - Find direct symlinks pointing outside a folder
Check whether direct symlink targets escape a deployment folder; unresolved links are reported separately.
node:fs/promises / node:path · Node.js 22+
Configuration · 2 tasks
- Detect duplicate keys in a simple dotenv file
Find keys accidentally assigned more than once without loading dotenv values into the process or logging secrets.
node:fs/promises · Node.js 22+ - Find duplicate listeners in a deployment plan
Inspect a JSON array of protocol, address and port objects for exact duplicate listeners. Wildcard and equivalent IPv6-address conflicts need separate review.
JSON · Node.js 22+
Web support · 2 tasks
- Summarise failed and slow requests from a HAR
Count failed and slow requests from a saved HAR without showing URLs, cookies, headers or bodies. No network replay.
JSON · Node.js 22+ - Check whether a source map embeds application code
Count embedded source-code entries in a flat version 3 source map without printing source paths or code. Indexed maps are rejected.
JSON · Node.js 22+
Package management · 1 tasks
- Count dependencies with installation hooks
Count package-lock v2/v3 records flagged with installation scripts before installation. A flag alone does not mean unsafe code.
package-lock.json · Node.js 22+
Web security · 1 tasks
- Review a captured HTTP response header baseline
Check key browser defence headers in a captured JSON object. Header presence does not prove a safe policy; no endpoint is contacted.
JSON · Node.js 22+
Data imports · 1 tasks
- Detect oversized nesting before a JSON import
Measure maximum JSON nesting and object/array counts before a constrained API import. Values and keys are not printed.
JSON · Node.js 22+
Monitoring · 1 tasks
- Find field-set changes in an event export
Compare top-level event field sets with the first NDJSON object. Report changed rows without printing keys or payload values.
JSON · Node.js 22+
DNS and certificates · 1 tasks
- Inspect certificate-authority DNS permissions
Query CAA records for one authorised domain. An empty direct answer does not rule out inherited parent policies.
node:dns/promises · Node.js 22+
Runtime diagnostics · 1 tasks
- Measure a five-second Node event-loop baseline
Measure scheduling delay in this process to establish a local baseline. This standalone script does not measure a different running application.
node:perf_hooks · Node.js 22+
Certificate dates are one check
A certificate validity-date report does not establish a trusted chain, hostname match or revocation status. Decide which checks your incident needs and verify them separately.
Official documentation ↗Guidance reviewed 11 October 2026. Script results still depend on permissions, installed versions and your environment.
SUPPORT PLAYBOOK
Investigate a slow Node.js service
Use the right measurement to distinguish a slow endpoint from a busy event loop.