If you're OK in having a node-esm
executable, please consider this solution.
#!/usr/bin/env sh
# the /usr/local/bin/node-esm executable
input_file=$1
shift
exec node --input-type=module - $@ <$input_file
#!/bin/bash | |
CYAN="$(tput bold; tput setaf 6)" | |
RESET="$(tput sgr0)" | |
clear | |
if command -v python3 > /dev/null 2>&1; then | |
if [ $(python3 -c "print('ye')") = "ye" ]; then | |
clear |
{ | |
"prepublishOnly": "if [[ ! $PWD =~ dist$ ]]; then npm run _dist:nopublish; fi", | |
"_dist:nopublish": "echo 'Use `npm run dist` instead of `npm publish`!' && exit 1", | |
"_dist:prep": "yarn build && cp package.json dist && cp README.md dist", | |
"_dist:post": "rm -f dist/package.json && rm -f dist/README.md", | |
"dist": "npm run _dist:prep && npm publish dist && npm run _dist:post" | |
} |
''' | |
parse SavedState artifacts extracted from OSX. | |
author: Willi Ballenthin ([email protected]) | |
license: Apache 2.0 | |
''' | |
import re | |
import sys | |
import json | |
import struct |
#!/bin/bash | |
set -e | |
declare -x USERNAME="$1" | |
declare -x USERPIC="$2" | |
declare -r DSIMPORT_CMD="/usr/bin/dsimport" | |
declare -r ID_CMD="/usr/bin/id" |
If you're OK in having a node-esm
executable, please consider this solution.
#!/usr/bin/env sh
# the /usr/local/bin/node-esm executable
input_file=$1
shift
exec node --input-type=module - $@ <$input_file
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
const user1 = { | |
id: 100, | |
name: 'Howard Moon', | |
password: 'Password!' | |
} | |
const removeProperty = prop => ({ [prop]: _, ...rest }) => rest | |
// ---- ------ | |
// \ / | |
// dynamic destructuring |
// Crypto Expansion Pack - Numi.io | |
numi.addUnit({ | |
"id": "wei", | |
"phrases": "wei, Wei", | |
"baseUnitId": "ETH", | |
"format": "Wei", | |
"ratio": 1e-18, | |
}); |
Git sees every file in your working copy as one of three things:
Ignored files are usually build artifacts and machine generated files that can be derived from your repository source or should otherwise not be committed. Some common examples are: