Psvensso

//Save this file in some Workspace util package like "utils", it will be used alot.

import React from "react";
export interface ICreateContextOptions {
    /**
     * If `true`, React will throw if context is `null` or `undefined`
     * In some cases, you might want to support nested context, so you can set it to `false`
     */
    strict?: boolean;
    /**

Psvensso

HTTPS=true
HOST='dev.local.io'
SSL_CRT_FILE=certificate.crt
SSL_KEY_FILE=certificate.key

Psvensso

import React from "react";

export const ServiceWorkerContext = React.createContext<{
  installedUpdate: boolean;
  waitingWorker: ServiceWorker | null;
}>({
  installedUpdate: false,
  waitingWorker: null,
});

Psvensso

SSL

The app uses SSL to work properly on mobile also on development. Webpack creates a .pem certificates but this is unstrusted in windows and you get the prompt on every resfresh.

One way to create a self signed certificate and force webpack to use locally created .pem cert and key.

1. Install "mkcert" https://github.com/FiloSottile/mkcert#windows (if needed install via Chocolatey)

2. Create a local folder somewhere outside the project, on the desktop for example

3. Generate certificate https://github.com/FiloSottile/mkcert#mkcert (use your domain names instead of example.com as they are showing in their readme)

Psvensso

type GetColorArgs = { index: number; outOf: number; };

export function getColor({ index, outOf }: GetColorArgs) {
    if (outOf < 1) {
        outOf = 1;
    }
    return "hsl(" + (index * (360 / outOf) % 360) + ",100%,50%)";
}

Psvensso

node --inspect-brk ./node_modules/.bin/webpack (or whatever file) to start the debugging process. The process will halt at the first line and print a debugger URL. Copy the debugger URL into the Chrome Browser and the developers tools will initialize.

Then go to the JavaScript profiler tab and start profiling After you've pressed stop, the flame graph will be generated.

If you don't want to copy debugger URLs around, you can also use the NIM chrome extension. It discovers debuggable node processes automatically.

Psvensso

function _t(){
    var result = "null";
    switch ("A") {
        case "A": {
            result += "A";
        }

        case "B":  {
            result += "B"; 
        }

Psvensso

{
  "defaultSeverity": "warning",
  "extends": [],
  "linterOptions": {
    "exclude": [
      "Scripts/typings/**/*.ts"
    ]
  },
  "rules": {
    "ban-types": {

Psvensso

import * as React from 'react';
export function getLocalStorageItem<T>(key: string, ifNull: T) {
    try {
        var item = localStorage.getItem(key);
        return item === null ? ifNull : JSON.parse(item);
    } catch (e) {
        localStorage.removeItem(key);
        return ifNull;
    }
}

Psvensso

Install Node.js V8 --inspector Manager (NiM) as a Chrome extension (work great!)
or start debugger listener manually or with some other tool. 

Then fire up your node process with the debugg flag.
node --inspect-brk ./somenodepath/webpack.js

Done.