Uladzimir Havenchyk havenchyk

Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

Use ESM yourself. (preferred)
Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
Stay on the existing version of the package until you can move to ESM.

File size checker

Prevents you from accidentially commenting very big assets. Make sure that you have optimized all your assets.

Installation

Add the script to your repo
Configure lint-staged

Ansible variable precedence

Source: http://docs.ansible.com/ansible/latest/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable

From least to most important

command line values (for example, -u my_user, these are not variables)
role defaults (defined in role/defaults/main.yml)
inventory file or script group vars
inventory group_vars/all

ESM modules in node: npm edition

The proposal you’re about to read is not just a proposal. We have a working implementation of almost everything we discussed here. We encourage you to checkout and build our branch: our fork, with the relevant branch selected. Building and using the implementation will give you a better understanding of what using it as a developer is like.

Our implementation ended up differing from the proposal on some minor points. As our last action item before making a PR, we’re writing documentation on what we did. While I loathe pointing to tests in lieu of documentation, they will be helpful until we complete writing docs: the unit tests.

This repo also contains a bundled version of npm that has a new command, asset. You can read the documentation for and goals of that comma

Promises as EventEmitters

I was trying to understand JavaScript Promises by using various libraries (bluebird, when, Q) and other async approaches.

I read the spec, some blog posts, and looked through some code. I learned how to

JavaScript Best Practicies

Short articles, references and checklists to keep control of application quality.

Common
- Babel
Browser specific
- Fast Load
- DOM
Server specific

	import * as React from 'react';
	import { useState } from 'react';
	import { useHistory } from 'react-router-dom';
	import useAsyncCallback from './useAsyncCallback';

	export default function LoginPage() {
	let history = useHistory();
	return (
	<article>
	{/* какой-то контент, всё что угодно на странице логина */}

	const now = new Date();
	const options = {
	timeZone: 'UTC',
	day: '2-digit',
	month: '2-digit',
	year: 'numeric'
	};
	const formatter = new Intl.DateTimeFormat("en-US", options);

	// mm-dd-yyyy with no library

	const range1 = len => Object.keys(new Int8Array(len)).map(parseFloat);

	const range2 = len => Array.apply(null, {length: len}).map(Number.call, Number);

	const range3 = (start, end) => Array.apply(null, Array(end - start)).map((_, i) => start + i);

	const range4 = (start, end) => [...Array(end - start)].map((_, i) => start + i);

	const range5 = len => Object.keys(Array.apply(null, Array(len)));

	// UPD:
	// Now available as npm module!
	// Check out https://github.com/RReverser/better-log for details.

	console.log = (function (log, inspect) {
	return function () {
	return log.apply(this, Array.prototype.map.call(arguments, function (arg) {
	return inspect(arg, { depth: 1, colors: true });
	}));
	};