burkeholland

Beast Mode

Beast Mode is a custom chat mode for VS Code agent that adds an opinionated workflow to the agent, including use of a todo list, extensive internet research capabilities, planning, tool usage instructions and more. Designed to be used with 4.1, although it will work with any model.

Below you will find the Beast Mode prompt in various versions - starting with the most recent - 3.1

Installation Instructions

• Go to the "agent" dropdown in VS Code chat sidebar and select "Configure Modes".
• Select "Create new custom chat mode file"

cheskoxd

import { useEffect, useRef } from 'react';

const useInactivityTimeout = (timeoutInHours) => {
  const timeoutInMillis = timeoutInHours * 60 * 60 * 1000;
  const timer = useRef(null);

  useEffect(() => {
    if (navigator.userActivation) {
      if(navigator.userActivation.isActive){        
        if (timer.current) {

phanan

<template>
  <VirtualScroller v-slot="{ item }" :item-height="35" :items="myMassiveArray">
    <div :item="item" :key="item.id">{{ item.details.i.guess? }}</div>
  </VirtualScroller>
</template>

danielroe

{
  "recommendations": [
    "aaron-bond.better-comments",
    "adrieankhisbe.vscode-ndjson",
    "johnsoncodehk.vscode-tsconfig-helper",
    "rbuckton.deoptexplorer-vscode",
    "helixquar.randomeverything",
    "WallabyJs.quokka-vscode",
    "bierner.comment-tagged-templates",
    "alexcvzz.vscode-sqlite",

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.

loilo

Vue: Pass Slots through from Parent to Child Components

The Situation

• We've got some components A, B and C which provide different slots.

  const A = {
    template: `<div><slot name="a">Default A Content</slot></div>`
  }

const B = {

davestewart

paulrouget

More details here: https://developer.mozilla.org/en/docs/Simple_Firefox_build

Hacking Firefox

Get Firefox' source code:

git clone https://github.com/mozilla/gecko-dev.git
git checkout fx-team

Install dependencies:

jrburke

Design forces:

• ECMAScript (ES) Module Loader API is coming. The ES module ID syntax are strings that are just treated as string IDs and not paths.
• Existing JS module experience in CommonJS/Node/AMD worlds of using module IDs that are resolved to a URL/path for fetching.
• Better package managers are coming for front end web apps. These package managers install assets by IDs not by paths.
• For front end code, baseURL + moduleID + '.js' is likely the default ID-to-URL resolution, but other declarative config could be possible for browser-based ES Module Loaders. Examples of useful declarative config in this area are the problems solved via common AMD loader config

So it will be common in JS code to use string IDs, and not URLs to refer to dependency resources.

With the coming of web components and custom elements, it will be possible for a custom element to depend on other custom e

jeresig

CookieClicker = {
	start: function() {
		this.clickInterval = setInterval(function(){
			// Click the large cookie as fast as possible!
			document.getElementById("bigCookie").click();
		}, 1);

		this.goldInterval = setInterval(function(){
			// Click the golden cookie
			var shimmer = document.getElementsByClassName("shimmer")[0];