These were provided to me by @feross at some point and then I tweaked them to work with slow internet, i.e. 1MBPS up.
I'm posting the the screenshots of those settings in the comments and I added two files that I found via File/Show Profile Folder
# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env | |
# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced | |
# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start | |
# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running. | |
# Add the following to your shell init to set up gpg-agent automatically for every shell | |
if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then | |
source ~/.gnupg/.gpg-agent-info | |
export GPG_AGENT_INFO | |
else |
npm users sorted by the monthly downloads of their modules, for the range May 6, 2018 until Jun 6, 2018.
Metrics are calculated using top-npm-users.
# | User | Downloads |
---|
`standard` is the 52th most depended on npm module. (counting dependencies and devDependencies) | |
-------- | |
SPECIFIC MODULES | |
-------- | |
standard 9860 | |
snazzy 1004 | |
eslint-config-standard 4235 |
mocha 44731 | |
chai 17944 | |
grunt 17447 | |
should 11882 | |
grunt-contrib-jshint 11466 | |
gulp 8619 | |
istanbul 7374 | |
tape 7313 | |
sinon 6851 | |
grunt-contrib-clean 6807 |
The standard code style linter is a great tool by Feross - check it out!
Remove trailing semicolons:
find . -path ./node_modules -prune -o -type f -name '*.js' -exec sed -i '' -e 's/;$//' {} \;
Ensure space between function
and opening bracket:
First, please read On Maintaining a Native Node Module
Problem: There is no standard way to build + distribute prebuilt binaries for node modules with native addons (e.g. C++ bindings).
There's a thing called NODE_MODULE_VERSION
which is used to know if a native module was compiled for the correct version + flavor of node. If you are trying to load something compiled for e.g. iojs
from February 2015 into node
from March 2014 you will get an error something like Error: Module version mismatch. Expected 11, got 42.
when you try and run your program. node
uses numbers from 10 going up, and iojs
uses numbers from 40 going up. The NODE_MODULE_VERSION
gets bumped usually when V8 is upgraded, but sometimes for other reasons. It also gets even more complicated when you start talking about runtimes like Electron or Node-Webkit, but I won't get into that here. To my knowledge there is n
NOTE I'm trying to find the most optimal fav/touch icon setup for my use-cases. Nothing new here. Read Mathias Bynens' articles on re-shortcut-icon and touch icons, a FAQ or a Cheat Sheet for all the details.
I'd like to hear how you approach this: @valuedstandards or comment on this gist.
You have to include a boatload of link
elements pointing to many different images to provide (mobile) devices with a 'favicon' or 'touch icon':