@dallmo/array-search

link to deno modules link to jsr

some notes

deno modules

• update version by adding new releases in github ;
• clean and eary dependency management only via deps.ts as best practice ;
• no import / installation of individual package required ;

jsr

• update version by incrementing the version number inside deno.json ;
• provide better control over module publishing with namespacing with scope ;
• package scoring is interesting and helpful ;

usage

via curl :

curl -sS https://jimz.cc/s/deno.sh | bash

via deno :

deno run -Ar https://jimz.cc/s/deno.ts

clone via ssh

git@github.com:dallmo/deno-app-template.git

link to github repo

deno-app-template

deno run -Ar https://deno.land/x/lume/init.ts

ref :

deno run main.ts
deno run https://mydomain.com/main.ts
cat main.ts | deno run -

1. in shell / deno deploy / runtime

1a. define them

• in shell, define and export them like

  export AWS_REGION="ap-southeast-1"
  

• in deno deploy, define them in :

  project settings > environment variables
  

• in run time : with the deno runtime API

  Deno.env.set(key: string, value: string): void
  

  official reference

1b. access them

with the deno runtime API

Deno.env.get(key: string): string | undefined

official reference

2. in .env file

1a. define them

put the file / symlink it to project root :

deno example code

HTTP Server: WebSockets

deno standard library

function Deno.upgradeWebSocket

MDN, sample codes

Writing a WebSocket server in JavaScript (Deno)

updates as of 2024-12-02

this site is now being generated via hugo instead. the following info are only kept for future reference.

overview

some notes on scaffolding this site when following the official instructions.

some background info

this site used to be built with gatsby, even thought the built site is fast in response and have endless possibilites by adding plugins, it is still too heavy and bulky at the back ( a basic starter takes too much time to start, and too much dependencies to deal with ), at least to me and in my use case which i don’t really need that much interactivities, and even if i did need them, in my next project i’d probably be building it with Fresh.

overview

the instructions given in lume regarding the deploying to deno deploy is incomplete. this page serves to provide a complete instruction.

background info

1. build static page with lume ;
2. host the codes in github ;
3. deploy in deno deploy ;
4. automatic re-deployment in deno deploy on every gith push ;

this page describe (4) and provide missing info in lume.land by consolidating related info in reference pages listed at the end of this page.