Add docs for dev imports #1754
Add docs for dev imports #1754
Conversation
| However, it can be useful to mark dev dependencies to aid people who are reading | ||
| your package. When using `deno.json`, the convention is to add a `// dev` | ||
| comment after any "dev only" dependency: |
There was a problem hiding this comment.
Nit, this requires you to rename deno.json to deno.jsonc
There was a problem hiding this comment.
Deno supports reading jsonc even in deno.json
There was a problem hiding this comment.
yeah but in Fresh we read deno.json to check if jsx is set correctly and stuff and we assume that .json means json and .jsonc means jsonc. There is probably more software out there with that assumption
There was a problem hiding this comment.
It might be good to update fresh to just always assume jsonc?
| [runtime will only load and install dependencies that are actually used in the | ||
| code that is being executed](#why-does-deno-not-have-a-devimports-field). |
There was a problem hiding this comment.
This isn't exactly true because for deno install it will install all the dependencies.
There was a problem hiding this comment.
This is clarified in the last paragraph of "Why does Deno not have a devImports field?"
| However, it can be useful to mark dev dependencies to aid people who are reading | ||
| your package. When using `deno.json`, the convention is to add a `// dev` | ||
| comment after any "dev only" dependency: |
There was a problem hiding this comment.
It might be good to update fresh to just always assume jsonc?
| { | ||
| "imports": { | ||
| "@std/fs": "jsr:@std/fs@1", | ||
| "@std/testing": "jsr:@std/testing@1" // dev |
No description provided.