everdimension

/**
 * Usage:
 * <Input customValidity="your validation message" /> // add constraint
 * or
 * <Input customValidity="" /> // remove constraint
 * or
 * <Input defaultCustomValidity="you message" /> // initial validationMessage
 */
export function Input({
  defaultCustomValidity,

igodorogea

Windows PC Setup

0. Prerequisites

Add Microsoft store
https://github.com/kkkgo/LTSC-Add-MicrosoftStore

Make sure winget is installed
https://github.com/microsoft/winget-cli#microsoft-store-recommended

mitchellh

I get asked pretty regularly what my opinion is on merge commits vs rebasing vs squashing. I've typed up this response so many times that I've decided to just put it in a gist so I can reference it whenever it comes up again.

I use merge, squash, rebase all situationally. I believe they all have their merits but their usage depends on the context. I think anyone who says any particular strategy is the right answer 100% of the time is wrong, but I think there is considerable acceptable leeway in when you use each. What follows is my personal and professional opinion:

khalidx

The experience of using Node.JS with TypeScript, ts-node, and ESM is horrible.

There are countless guides of how to integrate them, but none of them seem to work.

Here's what worked for me.

Just add the following files and run npm run dev. You'll be good to go!

package.json

unrevised6419

Google Spreadsheet function that shows rates from curs.md

Script was made for learning purposes
Please read terms curs.md: https://www.curs.md/ro/terms

How to add the function: https://developers.google.com/apps-script/guides/sheets
Rates are taken from: https://www.curs.md/ro/json_convertor_provider/default

Function signature

unrevised6419

Instant Markdown editor in new tab

1. Create a new bookmark
2. To the link add data:text/html,
3. After data:text/html, paste block below
4. Save bookmark, and open it

First time it may take a while to load the library

coolaj86

Can you convert a Value Object (i.e. JSON) to YAML?

My Expectation

My expectation is that a mid-senior level developer should be able to accomplish this task in under 4 hours:

• write a basic solution in 30-60 minutes
• debug / test / fine-tune for another 60-90 minutes
• document, package, and publish within the remaining time

I could see it reasonable even if a developer takes 2 days to solve this for the first time - possibly because they needed to take a break but didn't, such as feeling pressure and getting brain freeze, taking an initial wrong approach, over-thinking the problem, and then just keeping beating the dead horse, etc - especially if they've never had to work independently before.

mjackson

Redirects in React Router v6

An important part of "routing" is handling redirects. Redirects usually happen when you want to preserve an old link and send all the traffic bound for that destination to some new URL so you don't end up with broken links.

The way we recommend handling redirects has changed in React Router v6. This document explains why.

Background

In React Router v4/5 (they have the same API, you can read about why we had to bump the major version here) we had a <Redirect> component that you could use to tell the router when to automatically redirect to another URL. You might have used it like this:

DavidWells

import Analytics from 'analytics'
import onRouteChange from '@analytics/router-utils'

const persistPageViewsPlugin = {
  name: 'persist-page-data-plugin',
  page: ({ payload }) => {
    const { properties } = payload
    const pageView = {
      path: properties.path,
      title: properties.title,

jonathantneal

":" //#;exec /usr/bin/env node --input-type=module - $@<$0

import process from 'process'

const { argv } = process

console.log(argv)