27 lines
785 B
Org Mode
27 lines
785 B
Org Mode
|
* Scroll conventions
|
||
|
|
** Deno
|
||
|
|
Each Deno scroll:
|
||
|
|
|
||
|
|
- is an immediate subdirectory of ~./deno~
|
||
|
|
- contains a Deno lockfile
|
||
|
|
|
||
|
|
Unless you're trying to shoot yourself or downstream dep maintainers in the foot.
|
||
|
|
- contains a ~scroll.nix~ file
|
||
|
|
- defines ~cache-command~ field in ~scroll.nix~
|
||
|
|
|
||
|
|
~cache-command~ triggers Deno cache build, putting cache in $DENO_DIR.
|
||
|
|
- does not use JSR dependencies
|
||
|
|
|
||
|
|
They have heavily timestamped metadata and therefore do not support
|
||
|
|
reproducible builds.
|
||
|
|
- can use NPM dependencies
|
||
|
|
|
||
|
|
~.lock~, ~.json~ and ~.jsonc~ files are recursively hashed
|
||
|
|
to determine if the cache is updated.
|
||
|
|
|
||
|
|
In that case a new entry needs to be added in knownHashes.
|
||
|
|
|
||
|
|
All scrolls currently are to use the same Deno version defined by the flake.
|
||
|
|
|
||
|
|
See ~./deno-workflow.nix~ for details.
|