Byungjin Park (Claud) posquit0

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

NAVER DEVIEW 2017 Slides

키노트 영상

DAY 1

I have been an aggressive Kubernetes evangelist over the last few years. It has been the hammer with which I have approached almost all my deployments, and the one tool I have mentioned (shoved down clients throats) in almost all my foremost communications with clients, and it was my go to choice when I was mocking my first startup (saharacluster.com).

A few weeks ago Docker 1.13 was released and I was tasked with replicating a client's Kubernetes deployment on Swarm, more specifically testing running compose on Swarm.

And it was a dream!

All our apps were already dockerised and all I had to do was make a few modificatons to an existing compose file that I had used for testing before prior said deployment on Kubernetes.

And, with the ease with which I was able to expose our endpoints, manage volumes, handle networking, deploy and tear down the setup. I in all honesty see no reason to not use Swarm. No mission-critical feature, or incredibly convenient really nice to have feature in Kubernetes that I'm go

AWS 학습 링크집 시리즈

AWS 트레이닝 및 자격증 소개 http://bit.ly/aws-tnc-intro
AWS 학습 자료집 http://bit.ly/aws-study-resource
AWS 공인 솔루션스 아키텍트 - 어소시에이트 수험 가이드 http://bit.ly/sacertguide
AWS 공인 개발자 - 어소시에이트 수험 가이드 http://bit.ly/devcertguide
AWS 보안 관련 컨텐츠 모음집 http://bit.ly/secontents
AWS 기반 빅데이터 학습자료집 http://bit.ly/bdonaws
AWS 딥러닝 학습 자료 모음집 http://bit.ly/dlonaws
AWS The Machine Learning pipeline on AWS 교육 학습 자료집 http://bit.ly/ml-pipeline

AWS 학습 링크집 시리즈

AWS 학습 자료집 http://bit.ly/aws-study-resource
AWS 공인 솔루션스 아키텍트 - 어소시에이트 수험 가이드 http://bit.ly/sacertguide
AWS 공인 개발자 - 어소시에이트 수험 가이드 http://bit.ly/devcertguide
AWS 보안 관련 컨텐츠 모음집 http://bit.ly/seccontents

AWS 공인 개발자 - 어소시에이트 수험 가이드(http://bit.ly/devcertguide)

Not all random values are created equal - for security-related code, you need a specific kind of random value.

A summary of this article, if you don't want to read the entire thing:

Don't use Math.random(). There are extremely few cases where Math.random() is the right answer. Don't use it, unless you've read this entire article, and determined that it's necessary for your case.
Don't use crypto.getRandomBytes directly. While it's a CSPRNG, it's easy to bias the result when 'transforming' it, such that the output becomes more predictable.
If you want to generate random tokens or API keys: Use uuid, specifically the uuid.v4() method. Avoid node-uuid - it's not the same package, and doesn't produce reliably secure random values.
If you want to generate random numbers in a range: Use random-number-csprng.

You should seriously consider reading the entire article, though - it's

	#!/usr/bin/env bash


	STAGED_FILES=$(git diff --cached --name-only --diff-filter=ACM \| grep '\.jsx\?$')
	BIN_PATH="$(git rev-parse --show-toplevel)/node_modules/.bin"

	eslint() {
	ESLINT="$BIN_PATH/eslint"

	# Check for eslint

	/**
	* Example to refresh tokens using https://github.com/auth0/node-jsonwebtoken
	* It was requested to be introduced at as part of the jsonwebtoken library,
	* since we feel it does not add too much value but it will add code to mantain
	* we won't include it.
	*
	* I create this gist just to help those who want to auto-refresh JWTs.
	*/

	const jwt = require('jsonwebtoken');

	#!/bin/bash

	# vars
	[ -z "$NUM_WORKERS" ] && NUM_WORKERS=3

	# init swarm (need for service command); if not created
	docker node ls 2> /dev/null \| grep "Leader"
	if [ $? -ne 0 ]; then
	docker swarm init > /dev/null 2>&1
	fi

	#!/bin/bash
	cd "$(git rev-parse --show-toplevel)"
	ESLINT="node_modules/.bin/eslint"
	pwd

	if [[ ! -x "$ESLINT" ]]; then
	printf "\t\033[41mPlease install ESlint\033[0m (npm install eslint)\n"
	exit 1
	fi