jeffwhelpley

import { Component, Input, ElementRef, Renderer2, PLATFORM_ID } from '@angular/core';
import { isPlatformServer } from '@angular/common';
import { RequestResponseAdapter } from '@gethuman/adapters';
import { config } from '@gethuman/config';
import { GhWebState } from '@gethuman/state';

@Component({
    selector: 'icon',
    standalone: true,
    template: ``, // no content for <icon></icon> since we are setting a mask-image

jeffwhelpley

#!/bin/sh

# this is from https://deliciousbrains.com/ssl-certificate-authority-for-local-https-development/

if [ "$#" -ne 1 ]; then
    echo "Usage: Must supply a domain"
    exit 1
fi

# Change these as appropriate for your organization

jeffwhelpley

export async function exportData(projectId: string, clientEmail: string, privateKey: string) {
    const timestamp = moment().format('YYYY-MM-DD_x');
    const name = `projects/${projectId}/databases/(default)`;
    const outputUriPrefix = `gs://${projectId}.appspot.com/backups/${timestamp}`;

    const fsAdmin = new v1.FirestoreAdminClient({
        projectId,
        credentials: {
            client_email: clientEmail,
            private_key: privateKey

jeffwhelpley

class Cli

  def run

    # get the hash of fish data by scrapping the website (see further below)
    fish_hash = self.get_fish_hash

    # CLI stays in loop until user types quit
    is_cli_active = true
    while is_cli_active

jeffwhelpley

So, I ran into this nasty issue in the following situation:

1. Multiple TypeScript projects
2. Running Webpack (via Angular CLI) on web project
3. npm linking from my web project to other local projects
4. Common downstream dependencies that are referenced in multiple local projects such as rxjs, firebase, @angular/core, etc.

When I first tried to run Webpack (via the Angular CLI) in this situation it choked even though it worked fine without npm linking. Specifically, I got two types of errors/warnings:

jeffwhelpley

export function ClassDecorator(meta?: any): Function {
    return function (target: any) {
        let targetProto = target.prototype;
        let targetMeta = targetProto.__meta = targetProto.__meta || {};
        targetMeta.cls = meta;
    };
}

export function MethodDecorator(meta?: any): Function {
    return function (targetProto: any, methodName: string) {

jeffwhelpley

server {
       listen       80;
       server_name  dev.gethuman.com *.dev.gethuman.com;

       location / {
           proxy_pass               http://localhost:8181;
           proxy_set_header         Connection "";
           proxy_http_version       1.1;
           proxy_set_header         Host            $host;
           proxy_set_header         X-Real-IP       $remote_addr;

jeffwhelpley

// interface for Window
interface Window {
  // add some stuff here
}

let someMockWindowObject = {
  // add some mock functionality here
};

jeffwhelpley

module.exports = {
    model: function (postService, tokens, postUtil) {
        return postService.find({ where: { urlId: tokens.urlId }, findOne: true })
            .then(function (post) {
                return {
                    pageHead:       postUtil.getPageHeaderInfo(post),
                    post:           post,
                    noindex:        post.status === 'rejected' || !!post.duplicateOf
                };
            });

jeffwhelpley

I had a lot of issues trying to get continuation-local-storage (cls) working on a hapi.js app with pm2 in cluster_mode. Long story short, my mistake was wrapping cls around my server.start() when I should have been running it in a request handler. Here is the code you should use to get all this working:

var cls = require('continuation-local-storage');
var ns = cls.createNamespace('mySession');

var Hapi = require('hapi');
var server = new Hapi.Server();
server.connection({ port: 80 });