jamiebuilds

Idea: Flat file system for file-based routing

Personally I've never liked how tools like Remix or NextJS have mapped a nested file system to routes. Simple things like "I want to put this component in its own file" become annoying tasks.

I've always been a fan of "flatter" file systems, my files often look like this:

/App/

developit

finally-polyfill

A tiny ~150-byte polyfill for Promise.prototype.finally.

Useful for browsers that support Promise but not the .finally() method.

Usage

npm install finally-polyfill

developit

@developit/replaceall

~80b ponyfill for String.prototype.replaceAll() with good performance.

Why ponyfill? Because this is a proposal for a spec, and polyfilling it in-place before it gets solidified could break code that relies on an incorrect implementation.

Alternate Version

rauschma

Strings

String.prototype.*

None of the string methods modify this – they always return fresh strings.

• charAt(pos: number): string ^ES1

  Returns the character at index pos, as a string (JavaScript does not have a datatype for characters). str[i] is equivalent to str.charAt(i) and more concise (caveat: may not work on old engines).

rauschma

This content moved here: https://exploringjs.com/impatient-js/ch_arrays.html#quickref-arrays

ebidel

Moved to https://github.com/ebidel/puppeteer-examples

kitze

import produce from 'immer';
import {createStore} from 'redux';

const handleActions = (actionsMap, defaultState) => (
  state = defaultState,
  {type, payload}
) =>
  produce(state, draft => {
    const action = actionsMap[type];
    action && action(draft, payload);

ceejbot

ESM modules in node: npm edition

The proposal you’re about to read is not just a proposal. We have a working implementation of almost everything we discussed here. We encourage you to checkout and build our branch: our fork, with the relevant branch selected. Building and using the implementation will give you a better understanding of what using it as a developer is like.

Our implementation ended up differing from the proposal on some minor points. As our last action item before making a PR, we’re writing documentation on what we did. While I loathe pointing to tests in lieu of documentation, they will be helpful until we complete writing docs: the unit tests.

This repo also contains a bundled version of npm that has a new command, asset. You can read the documentation for and goals of that comma

ryanflorence

/* eslint no-undef: 0*/
/* eslint react/jsx-no-undef: 0*/
import React from "react"

const chart = {
  id: "purchase",
  initial: "fetchingWorkshopData",
  states: {
    fetchingWorkshopData: {
      on: {

tomkis

import { select, put, take } from 'redux-saga/effects';

function* emptySaga() {}

export function* withConfirmation(text, onConfirm, onCancel = emptySaga) {
  yield put({ type: 'ShowConfirmationDialog', payload: text });

  const { type } = yield take([
    'ConfirmationDialogConfirmed',
    'ConfirmationDialogCanceled'