Pankaj Patel pankajpatel

npm version cheatsheet

npm uses Semantic Versioning

npm uses Semantic Versioning. Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards compatible manner, and
PATCH version when you make backwards compatible bug fixes.

What Hiring Should Look Like

This is definitely not the first time I've written about this topic, but I haven't written formally about it in quite awhile. So I want to revisit why I think technical-position interviewing is so poorly designed, and lay out what I think would be a better process.

I'm just one guy, with a bunch of strong opinions and a bunch of flaws. So take these suggestions with a grain of salt. I'm sure there's a lot of talented, passionate folks with other thoughts, and some are probably a lot more interesting and useful than my own.

But at the same time, I hope you'll set aside the assumptions and status quo of how interviewing is always done. Just because you were hired a certain way, and even if you liked it, doesn't mean that it's a good interview process to repeat.

If you're happy with the way technical interviewing currently works at your company, fine. Just stop, don't read any further. I'm not going to spend any effort trying to convince you otherwise.

Egghead Workshop Notes

Notes from Build an App with React Suspense, Hooks, and Context Workshop Setup with Michael Chan

Write a detailed README with contact info, info about the workshop itself, license etc
Create a folder for each lesson so folks won’t have to struggle with switching git branches every 15 minutes
Give everyone a minute to process what they’ve learned and to figure out whether they have questions
Reference the docs so once the workshop concludes everyone knows where to find the resources to refresh what they’ve learned
As with egghead lessons, guide their eyes - if you’re explaining something, then select it in your IDE (at least hover over it)
Take a minute to go over the questions from the chat, read the question out loud
Don’t be afraid to experiment when there’s an interesting question, we’re all nerds here who love to try out new stuff

What is Plop

Plop is a file generator tool system which allows you to define a script file to generate all the boilerplate files for you. Similar in how Angular schematics works, you can define a set of actions who would generate all the pre-defined code for you either automatically or by answering to some CLI prompts. First you will need to define a plopfile.js who would contain a function who would receive a plop object with access to all the methods to generate the code.

module.exports = function (plop) {
    plop.setGenerator('components', {

How to create an HTTPS certificate for localhost domains

This focuses on generating the certificates for loading local virtual hosts hosted on your computer, for development only.

Do not use self-signed certificates in production ! For online certificates, use Let's Encrypt instead (tutorial).

Strings

`String.prototype.*`

None of the string methods modify this – they always return fresh strings.

charAt(pos: number): string ^ES1

Returns the character at index pos, as a string (JavaScript does not have a datatype for characters). str[i] is equivalent to str.charAt(i) and more concise (caveat: may not work on old engines).

	import styled from '@emotion/styled';
	import {
	Typography as MaterialTypography,
	TypographyProps as MaterialTypographyProps,
	} from '@material-ui/core';
	import {
	spacing,
	SpacingProps,
	sizing,
	SizingProps,

	:root {
	--grid-size: 10px;
	--cell-amount: 10;
	--grid-line-opacity: .4;
	--grid-offset-x: 20px;
	--grid-offset-y: 20px;
	}


	.with-grid-lines {

	.next/
	node_modules/
	Dockerfile
	yarn-error.log
	.dockerignore
	.git
	.gitignore

	.pnp.*
	.yarn/*
	!.yarn/patches
	!.yarn/plugins
	!.yarn/releases
	!.yarn/sdks
	!.yarn/versions