This website requires JavaScript.
Explore
Help
Sign in
foster
/
denoland-deno
Watch
1
Star
0
Fork
You've already forked denoland-deno
0
mirror of
https://github.com/denoland/deno.git
synced
2024-12-22 15:24:46 -05:00
Code
Issues
Packages
1
Wiki
Activity
8db420d552
denoland-deno
/
tests
/
specs
/
publish
/
package_json
/
package.json
8 lines
95 B
JSON
Raw
Normal View
History
Unescape
Escape
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
{
"name"
:
"@deno/foo"
,
"version"
:
"0.0.1"
,
"dependencies"
:
{
fix(publish): error for missing version constraints on dry-publish instead of just publish (#23798) Closes https://github.com/denoland/deno/issues/22835
2024-05-14 10:30:09 -04:00
"picocolors"
:
"1"
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
}
}
Copy permalink