dmmulroy

Below is the Effect 4 shape I’d create for a short top-level mlink CLI.

Commands

No links prefix:

  mlink health
  mlink list [--q] [--status active|tombstoned|all] [--kind alias|generated|all] [--limit] [--cursor] [--all]
  mlink get <slug>

benpsnyder

Drizzle ORM + Effect v4 — Bun and pnpm v11 patch

Status: Working patch for the exact combo drizzle-orm@1.0.0-beta.20 + drizzle-kit@1.0.0-beta.20 + effect@4.0.0-beta.42 + @effect/sql-pg@4.0.0-beta.42 Tested package managers: bun@1.3.12, pnpm@11.0.0-rc.0 Context: drizzle-team/drizzle-orm#5484 (unmerged PR), drizzle-team/drizzle-orm#5414 Scope: This gist is intentionally version-specific. If you move to a different Drizzle beta or different Effect beta, re-test or regenerate the patch.

Drizzle ORM 1.0 ships a built-in Effect integration at drizzle-orm/effect-postgres, but the published drizzle-orm@1.0.0-beta.20 package targets Effect v3 APIs. This patch updates that integration to work with Effect v4 for the exact versions above.

The patch file in this gist is manager-neutral. The patch contents work with both Bun and pnpm v11. What differs is only where

alexfazio

---

name: Hook Development description: >- This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "implement agent hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", "frontmatter hooks", "scoped hooks", "once: true", or mentions hook events (PreToolUse, PostToolUse, Stop,

moonflame

Page({
  data: {
    currentDate: new Date().getTime(),
    minDate: new Date().getTime()
  },

  onInput(event) {
    this.setData({
      currentDate: event.detail,
    });

yyx990803

2.6 Internal Change: Reverting nextTick to Always Use Microtask

The Original Problem

When Vue detects data mutation, it asynchronously defer DOM updates to the next "tick" so that multiple mutations trigger only one update cycle. In versions before 2.5, Vue has been deferring updates using what is known as the "Microtask" (as explained in this blog post).

This works fine in most situations, but we discovered an edge case:

1. Given two nested elements, "outer" and "inner";
2. "inner" has a click event handler which triggers an update

Ariex

// v3 is shorter than v2, and achieve same goal
(()=>{
    let Deferred = function(){
        let resolver, rejector,
            promise = new Promise((resolve, reject)=>{
                resolver = resolve;
                rejector = reject;
            });
        promise.resolve = d=>resolver(d);
        promise.reject = d=>rejector(d);

JoeNoPhoto

const addCounter = (list) => {
  return [...list, 0];
};

const removeCounter = (list, index) => {\
  return [
    ...list.slice(0, index),
    ...list.slice(index + 1)
  ];
};

dabblet.css

/**
 * The first commented line is your dabblet’s title
 */
 :root {    
    background-color: #6374AB;
    padding: 50px; 
 } 
ul{
	background:yellow;
	margin:0;

dypsilon

Frontend Development

Attention: the list was moved to

https://github.com/dypsilon/frontend-dev-bookmarks

This page is not maintained anymore, please update your bookmarks.

---

stephenplusplus

// Generated on <%= (new Date).toISOString().split('T')[0] %> using <%= pkg.name %> <%= pkg.version %>
'use strict';
var moment = require('moment');

var LIVERELOAD_PORT = 35729;
var lrSnippet = require('connect-livereload')({port: LIVERELOAD_PORT});
var mountFolder = function (connect, dir) {
  return connect.static(require('path').resolve(dir));
};