ctsin

let filepath = ''; // your actual filepath
let obj = {}; // your actual object
let response = JSON.stringify(obj, null, 2);

let query = `
    INSERT INTO imposters (filepath, response)
    VALUES (?, ?)
    ON DUPLICATE KEY UPDATE filepath = VALUES(filepath), response = VALUES(response);
`;

ctsin

The experience of using Node.JS with TypeScript, ts-node, and ESM is horrible.

There are countless guides of how to integrate them, but none of them seem to work.

Here's what worked for me.

Just add the following files and run npm run dev. You'll be good to go!

package.json

ctsin

Changes to Event Delegation

In React 16 and earlier, React attaches one handler per event type directly at the document node. If you ahve multiple React versions on the page, they all register event handlers at hte top. This breaks e.stopPropagation().

In React 17, React will no longer attach event handlers at the document level, Instead, it will attach then to the root DOM container into which your React tree is rendered.

const rootNode = document.getElementById('root');
ReactDOM.render(<App />, rootNode);

ctsin

.gitattributes

text=lf *.css linguist-vendored eol=lf *.scss linguist-vendored eol=lf *.js linguist-vendored eol=lf *.php eol=lf CHANGELOG.md export-ignore

~/.gitconfig

ctsin

https://dev.to/albertomontalesi/learn-pass-by-value-and-pass-by-reference-in-javascript-18ch

function increaseAge(person){
    person = {
        name: "Alberto",
        age: person.age + 1
    }
    console.log(person.age);
}

ctsin

https://indepth.dev/learn-to-combine-rxjs-sequences-with-super-intuitive-interactive-diagrams/

• merge => mergeAll => mergeMap
• concat => concatAll => concatMap
• switch => switchAll => switchMap

The High Order Obervable will emit error if any of inner Obervable gets error.

ctsin

// https://www.typescriptlang.org/play/?ssl=1&ssc=1&pln=7&pc=2#code/MYGwhgzhAEDC0G8BQ1XQHZgLYFNoF5oAKASgID4MBXEEAbhTTAHMcAuarAIxwCcG00YAHt0EAC68qwccN5EADrwCWANzDi8rdABM+HCSvTMyyQYPEALZRAB0LPIQCcTgWgC+Sd0A
// Babel will make a little bit different in properties order.
class C {
    name = () => null;
    age: number;
    constructor(private gender: string) {
        this.age = 99;
    }
}

ctsin

// https://alligator.io/angular/change-detection-strategy/

import { Component, Input, ChangeDetectionStrategy } from '@angular/core';

@Component({
  selector: 'app-child',
  templateUrl: './child.component.html',
  changeDetection: ChangeDetectionStrategy.OnPush
})
export class ChildComponent {

ctsin

// https://www.typescriptlang.org/docs/handbook/advanced-types.html#using-type-predicates

type DateVal = Record<'from' | 'to', string>

interface X {
  filed: boolean | DateVal
}

const x: X = { filed: true }

ctsin

/* eslint-disable no-unused-vars */
/* eslint-disable no-else-return */

// JSX constructor, similar to createElement()
export const h = (type, props, ...children) => {
	return {
		type,
		// Props will be an object for components and DOM nodes, but a string for
		// text nodes
		props,