noxasaxon

Learning Rust

Getting Started + Installation | Cheat Sheet

Table of Contents

1. How Do I Start Learning Rust?!
2. Ok, I Think I Know The Basics But How Do I Get Better?!
3. Rustlang Tooling
4. Helpful References Throughout Your Journey
5. The Rust Community
6. Recommended (but not free) Books & Courses

okikio

/** resolve.exports but for imports */
/**
 * @param {object} imports
 * @param {Set<string>} keys
 */
 function loop(imports, keys) {
	if (typeof imports === 'string') {
		return imports;
	}

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.

aleclarson

Features

🔥 Blazing fast builds
😇 CommonJS bundle
🌲 .mjs bundle
✨ .d.ts bundle + type-checking
🧐 Source maps

Install

sandren

Tailwind CSS best practices

Utility classes

1. When writing a string of multiple utility classes, always do so in an order with meaning. The "Concentric CSS" approach works well with utility classes (i.e,. 1. positioning/visibility 2. box model 3. borders 4. backgrounds 5. typography 6. other visual adjustments). Once you establish a familiar pattern of ordering, parsing through long strings of utility classes will become much, much faster so a little more effort up front goes a long way!

2. Always use fewer utility classes when possible. For example, use mx-2 instead of ml-2 mr-2 and don't be afraid to use the simpler p-4 lg:pt-8 instead of the longer, more complicated pt-4 lg:pt-8 pr-4 pb-4 pl-4.

3. Prefix all utility classes that will only apply at a certain breakpoint with that breakpoint's prefix. For example, use block lg:flex lg:flex-col lg:justify-center instead of block lg:flex flex-col justify-center to make it very clear that the flexbox utilities are only applicable at the

jeremyben

import * as path from 'path'
import ts from 'typescript'

function build(
	override: {
		compilerOptions?: ts.CompilerOptions
		include?: string[]
		exclude?: string[]
		files?: string[]
		extends?: string

cekstam

git log -n 10\
    --pretty=format:'{"commit": "%H", "author": "%aN <%aE>", "date": "%ai", "message": """%B""", "notes": """%N""" },' \
    $@  | awk 'BEGIN { print("[") } { print($0) } END { print("]") }' | python -u -c \
    'import ast,json,sys; print(json.dumps(ast.literal_eval(sys.stdin.read())))'

somebody32

Prerequisites

1. The app that uses tailwind + external component library (CL) (but not 3rdparty, your company internal one, for example)
2. The component library also uses tailwind

The goal

To be able to purge safely unused tailwind classes from the build (https://tailwindcss.com/docs/controlling-file-size)

Solution

The idea here is simple: we're going to purge css on the app side + whitelist classes that component library is using.

swyxio

Sequence of Gatsby's bootstrap lifecycle with links to source code as of v2.0.0

permalink https://github.com/gatsbyjs/gatsby/blob/ffd8b2d691c995c760fe380769852bcdb26a2278/packages/gatsby/src/bootstrap/index.js

1. open and validate gatsby-config (get-config-file.js) 1.5 load themes (swyx added this note July 2019)
2. load plugins (load-plugins/index.js) from the list given in gatsby-config.js
3. onPreBootstrap: runs onPreBootstrap if it is implemented in any plugins, for example gatsby-plugin-typography. Receives handy [apiCallArgs](https://github.com/gatsbyjs/gatsby/blob/ffd8b2d691c9

jackawatts

Getting Started

1. Install:

• jest: npm install --save-dev jest
• ts-jest: npm install --save-dev ts-jest @types/jest

2. Modify package.json

"jest": {
  "transform": {
 "^.+\\.tsx?$": "ts-jest"