nighthacker nighthacker

The experience of using Node.JS with TypeScript, ts-node, and ESM is horrible.

There are countless guides of how to integrate them, but none of them seem to work.

Here's what worked for me.

Just add the following files and run npm run dev. You'll be good to go!

`package.json`

Security Advisories / Bulletins / vendors Responses linked to Log4Shell (CVE-2021-44228)

Errors, typos, something to say ?

If you want to add a link, comment or send it to me
Feel free to report any mistake directly below in the comment or in DM on Twitter @SwitHak

Other great resources

Royce Williams list sorted by vendors responses Royce List
Very detailed list NCSC-NL
The list maintained by U.S. Cybersecurity and Infrastructure Security Agency: CISA List

Add Git Branch Name to Terminal Prompt (zsh)

Updated for MacOS with zsh

Catalina
Big Sur
Monterey
Ventura
Sonoma

Jenkins in Docker (docker-in-docker)

Testing Jenkins flows on your local machine, or running Jenkins in production in a docker container can be a little tricky with a docker-in-docker scenario. You could install Jenkins to avoid any docker-in-docker issues, but then you have Jenkins on your machine, and the local environment is likely going to be a fairly different from the actual production build servers, which can lead to annoying and time-consuming issues to debug.

Build environment differences are precisely why there is a strong argument to be made to run build processes strictly in docker containers. If we follow the philosophy that every build step or action should run in a docker container, even the Jenkins server itself, then we get massive benefits from things like, total control over the build environment, easily modify the build environment without the possibility of adversely effecting other jobs, explicit and strongly controlled tool versions,

Using Git Commit Message Templates to Write Better Commit Messages

The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the

Moved to Shopify/graphql-design-tutorial

	<?xml version="1.0"?>
	<ruleset name="Laravel Standards">

	<!--
	The name attribute of the ruleset tag is displayed
	when running PHP_CodeSniffer with the -v command line
	argument. The description tag below is not displayed anywhere
	except in this file, so it can contain information for
	developers who may change this file in the future.
	-->

	<?php
	namespace Deployer;

	require 'recipe/laravel.php';
	require 'vendor/deployer/recipes/local.php';
	require 'vendor/deployer/recipes/rsync.php';
	require 'vendor/deployer/recipes/npm.php';

	// Configuration
	set('ssh_type', 'native');

	# -- mode: ruby --

	# vi: set ft=ruby :

	boxes = [
	{
	:name => "server1",
	:eth1 => "192.168.205.10",
	:mem => "1024",
	:cpu => "1"