mirror of
https://github.com/denoland/deno.git
synced 2024-12-22 15:24:46 -05:00
cddefecfff
<!-- 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. |
||
---|---|---|
.. | ||
deno_jsonc | ||
has_slow_types | ||
invalid_import | ||
invalid_path | ||
javascript_decl_file | ||
javascript_missing_decl_file | ||
missing_deno_json | ||
node_specifier | ||
package_json | ||
successful | ||
symlink | ||
unanalyzable_dynamic_import | ||
workspace | ||
allow_slow_types.out | ||
deno_jsonc.out | ||
dry_run.out | ||
has_slow_types.out | ||
invalid_import.out | ||
invalid_path.out | ||
javascript_decl_file.out | ||
javascript_missing_decl_file.out | ||
missing_deno_json.out | ||
no_token.out | ||
node_specifier.out | ||
package_json.out | ||
successful.out | ||
successful_no_check.out | ||
symlink.out | ||
unanalyzable_dynamic_import.out | ||
workspace.out | ||
workspace_individual.out |