Marvin Hagemeister cddefecfff feat: infer dependencies from package.json (#22563) ... <!-- Before submitting a PR, please read https://docs.deno.com/runtime/manual/references/contributing 1. Give the PR a descriptive title. Examples of good title: - fix(std/http): Fix race condition in server - docs(console): Update docstrings - feat(doc): Handle nested reexports Examples of bad title: - fix #7123 - update docs - fix bugs 2. Ensure there is a related issue and it is referenced in the PR text. 3. Ensure there are tests that cover the changes. 4. Ensure `cargo test` passes. 5. Ensure `./tools/format.js` passes without changing files. 6. Ensure `./tools/lint.js` passes. 7. Open as a draft PR if your work is still in progress. The CI won't run all steps, but you can add '[ci]' to a commit message to force it to. 8. If you would like to run the benchmarks on the CI, add the 'ci-bench' label. --> This PR enhances the `deno publish` command to infer dependencies from `package.json` if present.		2024-02-23 15:56:49 +01:00
..
deno.json	feat: infer dependencies from package.json (#22563)	2024-02-23 15:56:49 +01:00
mod.ts	feat: infer dependencies from package.json (#22563)	2024-02-23 15:56:49 +01:00
package.json	feat: infer dependencies from package.json (#22563)	2024-02-23 15:56:49 +01:00