lemanschik / b8g-dev Goto Github PK

Like nixos and nix package manager but using git

takes a git approach to package management and system configuration. Learn how to make reproducible, declarative and reliable systems using the ECMAScript Module definition to define your Interfaces and API's.

Explain strings in deepth and UInt8Array and Type UInt8[]

bla bla utf8 bla bla emoticons bla bla 8 16 32 bits nosferatu
bla bla data views
bla bla data copy throw away inmutable original aka inmutable data.

show off template strings
show of taggedTemplateStringFunctions
show of regex including match ranges. ES2022

show of handling of package names and version

api versions only increment on part x.x if there are core changes security related changes to the core get always streamed in everything else is useless.

so your only allowed to use the first two parts the last part should be kept 0 to show that your a good coder with more skill then the most engineers

the file hash is the hash of the file without it self this is confusing but you can not do it better in that abstraction
best is to drop the json as soon as you can. ECMAScript

• hash publish under only tagname and only hashName

// Note the last .0 is needed you can only publish on npm with a incrementer
npm set package version "0.0.0-stable.0"
npm tag stable currentCommit hash package.json

npm:package@stable npm:package@commitHash

that allows u to reuse git references when targeting the repo via its latest commit to the package.json which often indicates that the repo is ready when it is a legacy repo

when it is a tooling driven repo often other indicators need to get used till you did abstract the core into its own part using the fundamentals of simplicity.

all this can get avoided via not using npm so as soon as you can come up with a package.json.js that generates the package.json for legacy tooling. You should avoid that if possible

ident alias pairs like in dependencies minify them

always keep in mind workspaces and packages are bad and they are not needed you can reference them by path inside your project and the files are versioned by git.

Git

clone bare

mkdir ~/repos
git clone gitUri ~/repos/org/repo.git
mkdir -p ~/worktree/org/repo && git clone --shared ~/repos/org/repo.git ~/worktree/org/repo
cd ~/worktree/org/repo

• https://git-scm.com/docs/git-submodule
• https://git-scm.com/docs/git-worktree
• git show
• git ls-tree

Basics of distributed Object Storage Databases Graphs B Trees and so on

Checkout with references

Use git clone -s. This will set up a writable repository which references the original repository's object store, so it will have a working tree index but won't store any objects of its own.

git clone --shared /path/to-bare-repo.git .