Notes for intro provided by commander_thrashdin.
(fun arg1 arg1 ...)
import path from 'path' | |
// 1. Define root of project from which to resolve all packages | |
const ROOT = path.resolve(__dirname, '..') | |
// 2. Define the relative path of the package that we generate the dorny filters for | |
const PACK = process.argv[2] | |
if (PACK == null) { | |
throw new Error( | |
'Need to supply relative path argument for package you want to render dorny filter for' |
// Run as a Chrome Snippetfrom either of the below urls: | |
// https://www.jazzradio.com/member/favorite/channels | |
// https://www.classicalradio.com/member/favorite/channels | |
// https://www.radiotunes.com/member/favorite/channels | |
// https://www.rockradio.com/member/favorite/channels | |
// https://www.zenradio.com/member/favorite/channels | |
const KEY = '<yourkeyhere>' | |
const subsidy = document.location.host.split('.')[1] | |
function getChannelInfos() { |
#!/usr/bin/env bash | |
## Prepare Wallets | |
solana-keygen new --silent --no-bip39-passphrase --outfile solpair1.json | |
solana-keygen new --silent --no-bip39-passphrase --outfile solpair2.json | |
### Airdrop and label them | |
amman airdrop ./solpair1.json -l soladdr1 |
Notes for intro provided by commander_thrashdin.
(fun arg1 arg1 ...)
http://05738ef0.ngrok.io |
I hereby claim:
To claim this, I am signing this object:
'use strict' | |
const deferred = { | |
resolve: function dontCare() {} | |
} | |
class DeoptMark { | |
constructor({ ITER = 1E3 } = {}) { | |
this._ITER = ITER | |
this._fns = [] |
The entire V8 compiler architecture as well as large parts of the Garbage Collector where updated recently. TurboFan replaced Crankshaft, Orinoco now collects garbage in parallel whenever possible. Node.js v8 shipped with this new and improved version of V8. As a result we can finally write idiomatic and declarative JavaScript without worrying about incurring performance overhead due to JavaScript compiler shortcomings.
At least this is what the V8 team tells us. In this talk we will explore if and why this is true, one demo at a time.
Tried to improve debugging when an express middleware is wrapped to auto-handle errors of an asnync
function.
Turns out the below reads a bit better than a return Promise.catch()
implementation, but still, once we reach the central express error handler, the line of the wrapped function that caused the error isn't included.
'use strict'