To enhance dependency administration, Deno 2.0 introduces a deno add subcommand to deal with specifiers with a subpath. As well as, if a venture accommodates a bundle.json file, Deno will want including npm: dependencies to bundle.json somewhat 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 attenuate diffs when updating dependencies and making certain reproducible builds. Moreover, Deno has improved error messaging, offering hints for widespread points reminiscent of incorrectly formatted relative import paths or lacking dependencies when utilizing “naked specifiers.” DenoLand stated the updates collectively streamline the method of managing dependencies in Deno tasks, making it extra intuitive and aligned with trendy growth 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 supplies a pull path to the principle module, has been relaxed and not requires full --allow-read permission. This additionally applies to the course of.argv API. It is also now attainable to grant permissions for studying and writing recordsdata that include commas within the file title.
Different new options and modifications in Deno 2.0: