⦇⦀∙ˇ∎ˇ∙⦀⦈ lxynox

People

`:bowtie:`	😄 `:smile:`	😆 `:laughing:`
😊 `:blush:`	😃 `:smiley:`	☺️ `:relaxed:`
😏 `:smirk:`	😍 `:heart_eyes:`	😘 `:kissing_heart:`
😚 `:kissing_closed_eyes:`	😳 `:flushed:`	😌 `:relieved:`
😆 `:satisfied:`	😁 `:grin:`	😉 `:wink:`
😜 `:stuck_out_tongue_winking_eye:`	😝 `:stuck_out_tongue_closed_eyes:`	😀 `:grinning:`
😗 `:kissing:`	😙 `:kissing_smiling_eyes:`	😛 `:stuck_out_tongue:`

Features

Add to home screen
Install banner
Offline support
App shell
Push notifications?
Background sync?
Server side rendering (SEO + improve First Meaningful Paint(FMP))

Features

Add to home screen
Install banner
Offline support
App shell
Push notifications?
Background sync?
Server side rendering (SEO + improve First Meaningful Paint(FMP))

WebSockets - An Introduction

WebSockets is a modern HTML5 standard which makes communication between client and server a lot more simpler than ever. We are all familiar with the technology of sockets. Sockets have been fundamental to network communication for a long time but usually the communication over the browser has been restricted. The general restrictions

The server used to have a permanent listener while the client (aka browser) was not designated any fixed listener for a more long term connection. Hence, every communication was restricted to the client demanding and the server responding.
This meant that unless the client requested for a particular resource, the server was unable to push such a resource to the client.
This was detrimental since the client is then forced to check with the server at regular intervals. This meant a lot of libraries focused on optimizing asynchronous calls and identifying the response of asynchronous calls. Notably t

When you create a npm package, remember it might be used in a browser or a server, or even a command line utility… For each package you create, please pay attention at what it will be used for:

Is it going to be used as a dependency to a nodejs application that is not bundled? (e.g. command line utilities)
Is it going to be used as a dependency to a nodejs application that is bundled? (e.g. AWS Lambdas)
Is it going to be used as a dependency to a browser application (always bundled)?.

In cases 2) and 3) you want to allow for tree shaking.
In cases 1) and 2) you want to benefit from the "ES6"/"ES next" features supported natively by nodejs.
In case 3) you also want to benefit from the native support of "ES6" from your browser.

	const COLORS = {
	blue: ['#1E88E5', '#90CAF9'],
	brown: ['#6D4C41', '#D7CCC8'],
	gray: ['#212121', '#BDBDBD'],
	green: ['#388E3C', '#A5D6A7'],
	red: ['#E53935', '#EF9A9A'],
	orange: ['#F4511E', '#FFAB91'],
	purple: ['#8E24AA', '#E1BEE7'],
	yellow: ['#FFD600', '#FFF59D'],
	}

	var el = document.createElement('script');
	el.src = "https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.10/lodash.core.min.js";
	el.type = "text/javascript";
	document.head.appendChild(el)