To enhance dependency administration, Deno 2.0 introduces a deno add subcommand to deal with specifiers with a subpath. As well as, if a undertaking accommodates a bundle.json file, Deno will choose including npm: dependencies to bundle.json relatively than deno.json. Builders can add “dev dependencies” to bundle.json utilizing the --dev flag. Additionally with Deno 2.0, deno set up now helps the --entrypoint flag, which permits for putting in all dependencies from a given module. And a brand new deno take away subcommand has been added to rapidly take away some dependencies. Deno 2.0 additionally ships with a extra concise lockfile format (v4) to reduce diffs when updating dependencies and guaranteeing reproducible builds. Moreover, Deno has improved error messaging, offering hints for frequent points comparable to incorrectly formatted relative import paths or lacking dependencies when utilizing “naked specifiers.” DenoLand mentioned the updates collectively streamline the method of managing dependencies in Deno initiatives, making it extra intuitive and aligned with fashionable improvement workflows.
The Deno permission system additionally will get consideration in Deno 2.0. With model 2.0, a scarcity of Deno permissions now raises the Deno.errors.Notcapable error as a substitute of Deno.errors.PermissionDenied, making it simpler to discriminate between OS-level errors and Deno errors. Additionally, the permissions verify for the Deno.mainModule API, which provides a pull path to the principle module, has been relaxed and now not requires full --allow-read permission. This additionally applies to the course of.argv API. It is also now potential to grant permissions for studying and writing recordsdata that comprise commas within the file title.
Different new options and modifications in Deno 2.0:
