sindresorhus

Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

1. Use ESM yourself. (preferred)
   Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
2. If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
3. Stay on the existing version of the package until you can move to ESM.

dcleao

NPM Commands, Scripts, Life-cycle Phases

The following describes the behaviour of several npm commands, particularly w.r.t. the scripts that are run in each, for NPM version 6.5.0.

npm build <other-package-folder>

1. npm run preinstall
2. link binaries (node-gyp)
3. for each bin command in other package:

moos

// per https://docs.npmjs.com/misc/scripts, npm exposes a bunch of variables to
// the environment prefixed with npm_config_*, npm_package_* and npm_lifecycle_*.
// Here's a list of all variables exposed in my setup.

npm_config_access=
npm_config_allow_same_version=
npm_config_also=
npm_config_always_auth=
npm_config_argv='{"remain":[],"cooked":["run","foo"],"original":["run","foo"]}'
npm_config_auth_type=legacy

nikcorg

Jake Archibald (@jaffathecake): The ServiceWorker is coming; look busy
https://speakerdeck.com/jaffathecake/the-serviceworker-is-coming-look-busy https://github.com/jakearchibald/trained-to-thrill/
https://www.youtube.com/watch?v=SmZ9XcTpMS4

Hunter Loftis (@hunterloftis): We Will All Be Game Progmrammers
http://wwabgp.herokuapp.com/s
http://youtu.be/QX0eauXBKwc

CarterRabasa (@carterrabasa): A Community of People; Not Projects

kriskowal

/*
Error
    at treachery (hell.js:49:11)
    at fraud (hell.js:45:12)
    at violence (hell.js:41:12)
    at heresy (hell.js:37:12)
    at anger (hell.js:33:12)
    at greed (hell.js:29:12)
    at gluttony (hell.js:25:12)
    at lust (hell.js:21:12)

vasilisvg

Group media queries on component level

The common way to use media queries is to group all styling for a specific query. Leenull, a colleague of mine, came with the idea to use media queries on a component level. This might make make complex stylesheets easier to maintain.

I wonder what you think of it. Please let me know in the comments. Here's a link to a working example.

Grouping on a component level looks like this

.item1 {

ericf

<?xml version="1.0" encoding="UTF-8"?>

<project name="cssembed" default="build_css">
    
    <!-- dirs -->
    <property name="libdir" value="${basedir}/lib" />
    <property name="sourcedir" value="${basedir}/source" />
    <property name="outputdir" value="${basedir}/build" />
    
    <!-- ant utils -->

padolsey

// ----------------------------------------------------------
// A short snippet for detecting versions of IE in JavaScript
// without resorting to user-agent sniffing
// ----------------------------------------------------------
// If you're not in IE (or IE version is less than 5) then:
//     ie === undefined
// If you're in IE (>=5) then you can determine which version:
//     ie === 7; // IE7
// Thus, to detect IE:
//     if (ie) {}

defunkt

Gist Clients

Want to create a Gist from your editor, the command line, or the Services menu? Here's how.

Editor Support

• TextMate
• Emacs
• Vim
• Coda

isaacs

// See comments below.

// This code sample and justification brought to you by
// Isaac Z. Schlueter, aka isaacs

// standard style
var a = "ape",
  b = "bat",
  c = "cat",
  d = "dog",