| // .babelrc | |
| // {"plugins": [["@babel/plugin-proposal-pipeline-operator", { "proposal": "minimal" }]]} | |
| const pipeable = (class_) => new Proxy({}, { | |
| get: (target, prop) => ( | |
| (prop in class_.prototype) | |
| ? (...args) => (receiver) => class_.prototype[prop].call(receiver, ...args) | |
| : class_[prop].bind(class_) // https://stackoverflow.com/a/30819436/5915221 | |
| ) | |
| }); |
| function createObservable(subscribe) { | |
| return { | |
| subscribe, | |
| pipe: function(operator) { | |
| return operator(this); | |
| }, | |
| }; | |
| } | |
| const numberObservable = createObservable(function(observer) { |
| /* | |
| Copy this into the console of any web page that is interactive and doesn't | |
| do hard reloads. You will hear your DOM changes as different pitches of | |
| audio. | |
| I have found this interesting for debugging, but also fun to hear web pages | |
| render like UIs do in movies. | |
| */ | |
| const audioCtx = new (window.AudioContext || window.webkitAudioContext)() |
When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');Those suck for maintenance and they're ugly.
| // Use Gists to store code you would like to remember later on | |
| console.log(window); // log the "window" object to the console |