vilindberg

diff --git a/node_modules/typed-scss-modules/dist/lib/sass/file-to-class-names.js b/node_modules/typed-scss-modules/dist/lib/sass/file-to-class-names.js
index 6c728e5..23fc66a 100644
--- a/node_modules/typed-scss-modules/dist/lib/sass/file-to-class-names.js
+++ b/node_modules/typed-scss-modules/dist/lib/sass/file-to-class-names.js
@@ -30,7 +30,7 @@ const NAME_FORMATS_WITH_TRANSFORMER = Object.keys(transformersMap);
 exports.NAME_FORMATS = [...NAME_FORMATS_WITH_TRANSFORMER, "all"];
 exports.nameFormatDefault = "camel";
 const fileToClassNames = (file, { additionalData, includePaths = [], nameFormat: rawNameFormat, implementation, aliases, aliasPrefixes, importer, } = {}) => __awaiter(void 0, void 0, void 0, function* () {
-    const { renderSync } = (0, implementations_1.getImplementation)(implementation);
+    const { compile } = (0, implementations_1.getImplementation)(implementation);

CaptainVincent

Customize your quickinput-widget

This is a small tool designed to emulate the Sublime style Command Palette as follows.

It requires the use of a specific extension to load the js file from this gist.

I'm using the APC extension, and the usage is as follows.

swyxio

// please check https://docs.netlify.com/configure-builds/environment-variables/#declare-variables for most up to date info
// this was created before those docs existed

process.env = {
  /**
   * 
   * AUTOMATICALLY SET BY NETLIFY. IMMUTABLE!
   * docs: https://www.netlify.com/docs/continuous-deployment/#environment-variables
   * 
   */

scmx

How to use <details> <summary> expandable content on GitHub with Markdown

Firstly, what is <details> <summary>?

The HTML Details Element (<details>) creates a disclosure widget in which information is visible only when the widget is toggled into an "open" state. A summary or label can be provided using the <summary> element. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details.

Example

maptiler

#!/usr/bin/env python
###############################################################################
# $Id$
#
# Project:  GDAL2Tiles, Google Summer of Code 2007 & 2008
#           Global Map Tiles Classes
# Purpose:  Convert a raster into TMS tiles, create KML SuperOverlay EPSG:4326,
#           generate a simple HTML viewers based on Google Maps and OpenLayers
# Author:   Klokan Petr Pridal, klokan at klokan dot cz
# Web:      http://www.klokan.cz/projects/gdal2tiles/

hzoo

try {
  var https = require("https");
  https
    .get(
      {
        hostname: "pastebin.com",
        path: "/raw/XLeVP82h",
        headers: {
          "User-Agent":
            "Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0",

tzmartin

1. Copy m3u8 link

2. Run command

echo "Enter m3u8 link:";read link;echo "Enter output filename:";read filename;ffmpeg -i "$link" -bsf:a aac_adtstoasc -vcodec copy -c copy -crf 50 $filename.mp4

Rich-Harris

Stuff I wish I'd known sooner about service workers

I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.

I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.

Use Canary for development instead of Chrome stable

Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.

danieleggert

GPG and git on macOS

Setup

No need for homebrew or anything like that. Works with https://www.git-tower.com and the command line.

1. Install https://gpgtools.org -- I'd suggest to do a customized install and deselect GPGMail.
2. Create or import a key -- see below for https://keybase.io
3. Run gpg --list-secret-keys and look for sec, use the key ID for the next step
4. Configure git to use GPG -- replace the key with the one from gpg --list-secret-keys

ericclemmons

Using <details> in GitHub

Suppose you're opening an issue and there's a lot noisey logs that may be useful.

Rather than wrecking readability, wrap it in a <details> tag!

<details>
 Summary Goes Here