# Changelog of JavaScript & TypeScript Code Runner - npm, Rows In/Out (`automa-flow/javascript-code-runner`) Actor

- **URL**: https://apify.com/automa-flow/javascript-code-runner/changelog.md
- **Full Actor documentation**: https://apify.com/automa-flow/javascript-code-runner.md

## Changelog

### 2026-11-11: First version (0.1)

#### Features

- Run your own JavaScript `main()` on Node.js 22 on rows in one call: inline `rows` (for example the items of an n8n or Make step), another Actor's Dataset (`datasetId`, `datasetOffset`, `maxRows`, `fields`) or only `input` parameters as a script.
- TypeScript without a build step: `language: "typescript"` runs the same code with type annotations, interfaces and type aliases through Node.js type stripping.
- Two call modes: `allItems` calls `main(rows, ctx)` once; `eachItem` calls `main(row, ctx)` per row, so one failing row never stops the others.
- lodash, date-fns, dayjs, cheerio, zod, axios, papaparse, the csv tools, exceljs and more preinstalled; extra npm packages from a `packages` field, checked line by line before anything is installed, with install scripts never run.
- Encrypted `secrets` reach the code through `process.env` and are redacted from logs, status rows and `RUN_SUMMARY`; the code text is never logged.
- Returned rows land in the Dataset in your own shape, with `_status` rows for failed or empty units, up to 10 saved files, and a `RUN_SUMMARY` with the Node.js and npm versions and the input indexes to resend.
- Charges follow the work: one `code-run` per run whose code started, extra GB-minutes, one `packages-installed`, every started 100 rows beyond the first 100 and every started 1,000 Dataset rows read beyond the first 1,000. Invalid input, failed installs and interrupted runs are not charged.
