Example text.
#!/bin/zsh | |
ext_root_path=~/Library/Application\ Support/Google/Chrome/Default/Extensions | |
find "$ext_root_path" -name "manifest.json" -print0 | while IFS= read -r -d '' file; do echo "\033[1;33m$file\033[0m"; echo "-----------------"; cat "$file" | nl -n ln | GREP_COLOR='01;30' grep --color=always '.*'; echo "-----------------"; done | |
# Prompt the user for the working directory path which is chrome extension root | |
read -p "Enter the chrome extension path(for example difoiogjjojoaoomphldepapgpbgkhkb/2.7.7_0): " workdir | |
# Prompt the user for the result app name | |
read -p "Enter the desired app name: " app_name |
const INCOME = 100_000; | |
// ----- 2022 ----- // | |
// https://www.canada.ca/en/revenue-agency/services/forms-publications/payroll/t4032-payroll-deductions-tables/t4032on-jan/t4032on-january-general-information.html | |
const CPP_BRACKETS = [ | |
[ 3_500, 0 ], // exemption | |
[ 61_400, 0.0570], // cap | |
[Infinity, 0 ], |
Now that Electron has hit Chrome's 60s we can have proper module support. But of course, the standard (for very good reasons) prevents loading modules from file:
and it makes sense for both Electron and NW.js to adhere to the statusquo.
So if you were really excited and this bums you, don't worry, you are in for awesome things.
The future Electron eco-system offers two options for native ES modules:
-
Custom Electron protocol via Chromium's module loading subsystem
-
Custom NodeJS loaders via Node's module loading subsystem recommended
A template-based BNF parser inspired by [@kach/nearly][].
I'm starting by cleaning up the nearly/nearly.js source code.
export class Rule {
This experiment demonstrates using a GitHub Gist to track and statically stage experimental code through a GitHub Pages.
Please refer to @SMotaal/experiments for more details.
<html> | |
<head> | |
<title>SMotaal's TEQ</title> | |
<meta charset="utf-8" /> | |
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover" /> | |
<meta name="theme-color" content="#262f36" /> | |
<meta name="background-color" content="#999999" /> | |
<link rel="stylesheet" href="/markout/styles/fonts/iosevka.css" /> | |
<link rel="stylesheet" href="/markout/styles/root.css" /> |
export default (class { | |
MakeInlineClosure() { | |
const messages = []; | |
return (message => { { messages.push(message); } }); | |
} | |
['InlineClosure (ahead-of-time)'] = ({MakeInlineClosure, InlineClosure = MakeInlineClosure()} = this) => () => InlineClosure('test'); | |
['InlineClosure (just-in-time)'] = ({MakeInlineClosure} = this) => () => MakeInlineClosure()('test'); |
-
Navigate to https://emojipedia.org/apple/ios-13.3/
-
Generate the asset manifest by running:
copy(JSON.stringify(Object.fromEntries([...document.querySelector('ul.emoji-grid').querySelectorAll('img[title][src][srcset]')].map(({title, attributes}, index) => ([attributes.title.value, attributes.srcset.value.replace(/ +\dx$/, '')])))))