orta

This is a work in progress. Please don't take this as something that will definitely happen, we all know what happens to well laid plans and I need to present it to the rest of the TypeScript team in order to figure out a lot of feasibility questions.

Intro

The examples in this PR assumes [CLI DX] Improve positioning of compiler error messaging info #45717 is merged

In 4.4, all diagnostic messages from TypeScript are treated the same, we have a massive .JSON file of ±2000 diagnostic messages which are used everywhere from compiler messages to CLI help. Aside from some simple string manipulation, these are effectively what we output for all error messages. I'd like to propose that we break this pattern, just for error TS2322.

TS2322 is our 'type x is not assignable to y' error, you'd see it for const str: string = 123 and I expect it is the most seen

Wattenberger

#!/bin/bash

# This script will download the contents of a GitHub repo
# and place them in a local directory.
#
# Usage:
#   download-repo.sh <repo> <output-path> <nested-path> <branch-name>
#
# Example:
#   download-repo.sh wattenberger/kumiko ./kumiko-assets master public/assets

jamiebuilds

Object.has()

This has been moved to https://github.com/jamiebuilds/proposal-object-has

pi0

const Webpackbar = require('webpackbar')

module.exports = {
  webpack: (config, { isServer }) => {
    config.plugins.push(new Webpackbar({ name: isServer ? 'server' : 'client' }))
    return config
  }
}

kyleshevlin

// The gotcha
function List({ items }) {
  return (
    items.length && items.map((item) => <Item key={item.id} item={item} />)
  );
}

// What will happen when the length of `items` is 0?

// It'll render a 0 as text in a Text Node, because JSX has to be able

ryanflorence

<LoadingButton
  ariaErrorAlert={"There was an error creating your account"}
  ariaLoadingAlert={
    authState === AuthState.CreatingUser
      ? "Registering account, please wait..."
      : authState === AuthState.FulfillingPurchase
      ? "Generating license, please wait..."
      : "Loading..."
  }
  ariaSuccessAlert="Account created! Redirecting."

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.

tkadlec

:root {
 --violation-color: red; /* used for clear issues */
 --warning-color: orange; /* used for potential issues we should look into */
}

/* IMAGES */

/*
 * Lazy-Loaded Images Check
 * ====

threepointone

On implementing a client for feature flags in your UI codebase

This document isn't an explainer on Feature Flags, you can find that with my amateur writeup, or literally hundreds of better writeups out there.

This document is also agnostic to the choice of service you'd use: LaunchDarkly or split.io or optimizely or whatever; that's orthogonal to this conversation.

Instead, this document is a list of considerations for implementing a client for using Feature Flags for User Interface development. Service providers usually give a simple fetch and use client and that's it; I contend that there's a lot more to care about. Let's dive in.

To encourage usage, we'd like for the developer experience to be as brutally simple as possible. So, this should be valid usage:

oliverjumpertz

<dialog open>
  <form method="dialog">
    <p>Do you want to confirm your action?</p>
    <div class="right">
      <input class="btn" type="submit" value="Ok" />
      <input class ="btn" type="submit" value="Cancel" />
    </div>
  </form>
</dialog>