fgnass

Goal

The goal is to package a server-side rendered Next.js app as SPA for capacitor.

Approach

Pages with dynamic routes/data use getServerSideProps(). For capacitor we need at least one page that can be rendered statically, preferably the index page.

When there are pages that use getServerSiedeProps() we can't use next export (it will fail with an error).

adriang133

#!/usr/bin/osascript
tell application "System Preferences"
  activate
end tell

tell application "System Events"
  tell process "System Preferences"
    activate
    delay 1
    click menu item "Displays" of menu "View" of menu bar 1

nickcernis

Exclude node_modules and .git from Backblaze backups on Mac

1. Edit the file at /Library/Backblaze.bzpkg/bzdata/bzexcluderules_editable.xml.
2. Add these rules inside the bzexclusions tag:

<!-- Exclude node_modules. -->
<excludefname_rule plat="mac" osVers="*"  ruleIsOptional="t" skipFirstCharThenStartsWith="users/" contains_1="/node_modules/" contains_2="*" doesNotContain="*" endsWith="*" hasFileExtension="*" />
<excludefname_rule plat="mac" osVers="*"  ruleIsOptional="t" skipFirstCharThenStartsWith="users/" contains_1="/.git/" contains_2="*" doesNotContain="*" endsWith="*" hasFileExtension="*" />

jtanx

[
  {
      "key": "ctrl+shift+tab",
      "command": "workbench.action.previousEditor"
  },
  {
      "key": "ctrl+tab",
      "command": "workbench.action.nextEditor"
  }
]

tibdex

/**
 * This codemod expects 2 CLI arguments:
 *  - packageDir: the path of the directory containing the package.json. It's used to detect whether a path points
 *    to a dependency or an internal module.
 *  - rootDirs: root directory paths separated by a comma if you have more than one root.
 *    Let's say that you have two files:
 *      - src/component.js
 *      - src/index.js containing the import "import Component from 'component.js';"
 *    To have the transformation successfully working you need to call jscodeshift with the "--rootDirs ./src" argument.
 */

hassanjamal

echo ".DS_Store" >> ~/.gitignore_global
echo "._.DS_Store" >> ~/.gitignore_global
echo "**/.DS_Store" >> ~/.gitignore_global
echo "**/._.DS_Store" >> ~/.gitignore_global
git config --global core.excludesfile ~/.gitignore_global

michiel

$ tmux attach
protocol version mismatch (client 7, server 6)

$ pgrep tmux
3429
$ /proc/3429/exe attach

gaearon

import React, { Component } from 'react'
import Subapp from './subapp/Root'

class BigApp extends Component {
  render() {
    return (
      <div>
        <Subapp />
        <Subapp />
        <Subapp />

jrichardlai

#!/bin/bash -x
find . -name 'fbjs' -print | grep "\./node_modules/fbjs" -v | xargs rm -rf

paulirish

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.

Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.

Element APIs

Getting box metrics

• elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent