// Dev tasks
{
"scripts": {
"eslint": "eslint --cache --fix ./",
"stylelint": "stylelint '**/*.scss' --syntax scss",
If you use server rendering, keep in mind that neither useLayoutEffect
nor useEffect
can run until the JavaScript is downloaded.
You might see a warning if you try to useLayoutEffect
on the server. Here's two common ways to fix it.
If this effect isn't important for first render (i.e. if the UI still looks valid before it runs), then useEffect
instead.
function MyComponent() {
If you use server rendering, keep in mind that neither useLayoutEffect
nor useEffect
can run until the JavaScript is downloaded.
You might see a warning if you try to useLayoutEffect
on the server. Here's two common ways to fix it.
If this effect isn't important for first render (i.e. if the UI still looks valid before it runs), then useEffect
instead.
function MyComponent() {
Steps to deploy a Node.js app to DigitalOcean using PM2, NGINX as a reverse proxy and an SSL from LetsEncrypt
If you use the referal link below, you get $10 free (1 or 2 months) https://m.do.co/c/5424d440c63a
I will be using the root user, but would suggest creating a new user
- Read the concept of TCP in this wiki page and try to understand all the concepts of it (deeply):
# Source: https://gist.github.com/48f44d3974db698d3127f52b6e7cd0d3 | |
########################################################### | |
# Automation of Everything # | |
# How To Combine Argo Events, Workflows, CD, and Rollouts # | |
# https://youtu.be/XNXJtxkUKeY # | |
########################################################### | |
# Requirements: | |
# - k8s v1.19+ cluster with nginx Ingress |
# Source: https://gist.github.com/764b402c8979678dfde01fd8f63c22e2 | |
########################################################### | |
# Kustomize vs Helm # | |
# The Fight Between Templating and Patching in Kubernetes # | |
# https://youtu.be/ZMFYSm0ldQ0 # | |
########################################################### | |
# Links to referenced videos: | |
# - https://youtu.be/sUPkGChvD54 |
Zach Caceres
Javascript does not have the typical 'private' and 'public' specifiers of more traditional object oriented languages like C# or Java. However, you can achieve the same effect through the clever application of Javascript's function-level scoping. The Revealing Module pattern is a design pattern for Javascript applications that elegantly solves this problem.
The central principle of the Revealing Module pattern is that all functionality and variables should be hidden unless deliberately exposed.
Let's imagine we have a music application where a musicPlayer.js file handles much of our user's experience. We need to access some methods, but shouldn't be able to mess with other methods or variables.
FWIW: I'm not the author of the content presented here (which is an outline from Edmond Lau's book). I've just copy-pasted it from somewhere over the Internet, but I cannot remember what exactly the original source is. I was also not able to find the author's name, so I cannot give him/her the proper credits.
- By Edmond Lau
- Highly Recommended 👍
- http://www.theeffectiveengineer.com/