This little guide describes what to do when:
- You see a vulnerability warning for a package, and
- The package has already been fixed, and a patch version has been released.
- Delete all lock files
# import config. | |
# You can change the default config with `make cnf="config_special.env" build` | |
cnf ?= config.env | |
include $(cnf) | |
export $(shell sed 's/=.*//' $(cnf)) | |
# import deploy config | |
# You can change the default deploy config with `make cnf="deploy_special.env" release` | |
dpl ?= deploy.env | |
include $(dpl) |
'use strict'; | |
const fs = require('fs'); | |
const path = require('path'); | |
module.exports = name => { | |
const datapath = path.join(__dirname, `${name}.json`); | |
const history = []; | |
const record = (input, key) => { |
const NEWLINE_REGEX = /\r?\n/; | |
const INCLUDE_REGEX = /^(\s*)include\(([A-Z][0-9a-zA-Z]*?)\)/; | |
const SECTION_START_REGEX = /^([a-z]+) ([A-Z][0-9a-zA-Z]*?)\s*{/; | |
const SECTION_END_REGEX = /(?<=})/; | |
class Section { | |
type = ''; | |
name = ''; | |
leading = []; | |
body = []; |
This little guide describes what to do when:
The code and instructions in this gist are from http://peterdowns.com/posts/open-iterm-finder-service.html. I've had to do this a few times and wanted to distill it the basics.
Automator
Application
Actions > Utilities > Run Applescript
open_in_iterm.app
into the window.Among other cherished values, the First Amendment protects freedom of speech. The U.S. Supreme Court often has struggled to determine what exactly constitutes protected speech. The following are examples of speech, both direct (words) and symbolic (actions), that the Court has decided are either entitled to First Amendment protections, or not.
Thanks for choosing to contribute to Enquirer! We're so happy that you're contributing to open source projects, and we're even happier that one of those projects is ours!
There is no faster, more effective way to improve a product than from the feedback from the first experience of a new user -- Jon Schlinkert
(This is an excerpt from a much longer paper I'm writing about code quality and maintaining FOSS projects.)
In an effort to improve the quality of search results on sites like https://npmjs.com, there has been more and more discussion about factoring in the ranking/scoring of dependencies to influence search results. The general idea is that a library should be ranked not only on its own merits, but dependencies should weigh into the score as well.
I’m not sure what my opinion is on this yet. I was initially in favor of this, and still might be, but this document is a summary of some things that crossed my mind about the topic.
Should dependencies weigh into the search score for a library?
<?xml version="1.0" encoding="UTF-8"?> | |
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> | |
<plist version="1.0"> | |
<dict> | |
<key>Ansi 0 Color</key> | |
<dict> | |
<key>Alpha Component</key> | |
<real>1</real> | |
<key>Blue Component</key> | |
<real>0.13333329558372498</real> |