denoland / denoland/deno_docker
What about deno.lock?
- Dominant language
- Dockerfile
- Stars
- 1k
- Forks
- 113
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
In this whole repo there is no mention of `deno.lock` - I'm a bit uncertain how to include it.
Also, do I have to import stuff into a `deps.ts` file in order to do the caching as described?
Feels like a weird way to define dependencies :thinking:
I also found [this reddit](https://www.reddit.com/r/Deno/comments/1g6btdr/is_depsts_still_the_recommended_way_to_deal_with/) thread, suggesting that `deno.jsonc`'s imports are a better replacement for `deps.ts` :thinking:
Contributor guide
No contributing guide indexed for this repository
Research direction
Search the repository for references to deno.lock, deps.ts, and deno.jsonc, then review how dependencies and caching are currently described. Determine which dependency-management approach the repository intends to support and document how deno.lock and dependency imports should be handled; done means the issue's questions have an explicit, repository-supported answer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100