denoland-deno/tests/specs/publish/package_json/package_json.out

Download http://localhost:4260/picocolors
Download http://localhost:4260/picocolors/picocolors-1.0.0.tgz
Check file:///[WILDCARD]/publish/package_json/mod.ts
Checking for slow types in the public API...
Check file:///[WILDCARD]/publish/package_json/mod.ts
Publishing @foo/bar@1.0.0 ...
Successfully published @foo/bar@1.0.0
Visit http://127.0.0.1:4250/@foo/bar@1.0.0 for details
chore: fix flaky net_listen_allow_localhost_4555 (#23726) Moves the test npm registry server port from `4558` to `426x` 2024-05-07 13:21:56 -04:00			`Download http://localhost:4260/picocolors`
			`Download http://localhost:4260/picocolors/picocolors-1.0.0.tgz`
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 09:56:49 -05:00			`Check file:///[WILDCARD]/publish/package_json/mod.ts`
			`Checking for slow types in the public API...`
			`Check file:///[WILDCARD]/publish/package_json/mod.ts`
			`Publishing @foo/bar@1.0.0 ...`
			`Successfully published @foo/bar@1.0.0`
			`Visit http://127.0.0.1:4250/@foo/bar@1.0.0 for details`