Documentation Feedback

Path: /runtime/fundamentals/configuration/
Helpful: Yes ✅

Feedback:

• https://docs.deno.com/runtime/fundamentals/configuration/#package.json-support - Rather than headlining deno.json and package.json as two types of supported configuration, we could more concisely say: "Here's how Deno projects are idiomatically configured, but note that Node.js projects with a package.json will generally work out-of-the-box". And then as we currently do, bring it up again in the dependencies and tasks sections.

• https://docs.deno.com/runtime/fundamentals/configuration/#proxies - This section feels out of place. Maybe we can just link to the environment variables page here https://docs.deno.com/runtime/reference/env_variables/.

• I keep getting frustrated that sections aren't titled by the configuration field key in code tags. But it's not always applicable.

GitHub User: @nayeemrmn

This issue was automatically created from the documentation feedback system.