Deno adds workspaces for managing monorepos

The latest update to the Deno TypeScript /JavaScript and WebAssembly runtime features workspace support along with Node.js compatibility improvements.

Deno 1.45 was introduced July 11. The release introduces workspaces for managing monorepos, simplifying dependency management, configuration sharing, and module organization across large code bases, Deno Land said. There are two forms of supported workspaces: Deno-first workspaces defined in deno.json and backwards-compatible NPM workspaces. Global configuration for these workspaces is applied to each member package but can be overridden by members. Developers can mix and match NPM and Deno workspaces, with an NPM package inside a Deno workspace or vice versa.

For Node.js compatibility, Node-API support has been revamped, fixing issues with packages such as prisma, sqlite3,  and  paper. Other Node.js compatibility improvements include working on support for dd.trace and support for fs.lutimes and fs.lutimesSync. Also, node:crypto and node:zlib were added. The node:http module was updated, with capabilities such as Server#close() now doing a graceful shutdown, allowing in-flight requests to finish. In another improvement, the node:vm will consume less memory. For NPM support, types shipped with the package are now preferred over types from @types scope.

Deno 1.45 makes the language server more independent of the foot folder open in the editor. Configuration files in subdirectories now are detected, even if there are multiple ones. Elsewhere in Deno 1.45, a new --frozen (alias --frozen-lockfile) has been added to control the behavior of the lockfile. This flag can be used to tell Deno to error out anytime the lockfile gets out of date. This is especially useful in Continuous Integration pipelines, Deno Land said. Also, Deno 1.45 ships with version 12.7 of the Google V8 JavaScript and WebAssembly engine and version 5.5.2 of TypeScript.