Francisco Caballero fjcero

$pageTitle

Allows to control the page title from the AngularJS route system, controllers or any other component through an injectable service.

ngPageTitle - Page title service (run tests)

To get started add the module to your app and configure the page title provider:

Installation for GUI Users

Right click the file and choose information and choose to always open this file with Terminal.app
Go to the Terminal.app and do something like this chmod 744 Reset Spotlight.sh
There you go, you can now double click it so reset the Spotlight location
Optional: Uncomment line for the useCount to prevent Spotlight to forget that you already used it

On implementing a client for feature flags in your UI codebase

This document isn't an explainer on Feature Flags, you can find that with my amateur writeup, or literally hundreds of better writeups out there.

This document is also agnostic to the choice of service you'd use: LaunchDarkly or split.io or optimizely or whatever; that's orthogonal to this conversation.

Instead, this document is a list of considerations for implementing a client for using Feature Flags for User Interface development. Service providers usually give a simple fetch and use client and that's it; I contend that there's a lot more to care about. Let's dive in.

To encourage usage, we'd like for the developer experience to be as brutally simple as possible. So, this should be valid usage:

ES Modules are terrible, actually

This post was adapted from an earlier Twitter thread.

It's incredible how many collective developer hours have been wasted on pushing through the turd that is ES Modules (often mistakenly called "ES6 Modules"). Causing a big ecosystem divide and massive tooling support issues, for... well, no reason, really. There are no actual advantages to it. At all.

It looks shiny and new and some libraries use it in their documentation without any explanation, so people assume that it's the new thing that must be used. And then I end up having to explain to them why, unlike CommonJS, it doesn't actually work everywhere yet, and may never do so. For example, you can't import ESM modules from a CommonJS file! (Update: I've released a module that works around this issue.)

And then there's Rollup, which apparently requires ESM to be u

	var child_process = require('child_process');

	exports.handler = function(event, context) {
	var proc = spawn('./test', [ JSON.stringify(event) ], { stdio: 'inherit' });

	proc.on('close', function(code){
	if(code !== 0) {
	return context.done(new Error("Process exited with non-zero status code"));
	}

	upstream ws_server {
	server 127.0.0.1:8080;
	}

	server {
	listen 80;
	server_name 10.1.2.225;

	location / {
	proxy_pass http://ws_server/;