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

{
  // Disable telemetry
  "telemetry.telemetryLevel": "off",
  // Zen mode
  "zenMode.fullScreen": false,
  "zenMode.hideTabs": true,
  "zenMode.centerLayout": false,
  // Theming
  "workbench.iconTheme": "city-lights-icons-vsc",
  "editor.fontFamily": "Dank Mono",

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];

Integralist

The BBC has a server-side image service which provides developers with multiple sized versions of any image they request. It works in a similar fashion to http://placehold.it/ but it also handles the image ratios returned (where as placehold.it doesn't).

The original BBC News process (and my re-working of the script) follows roughly these steps...

• Create new instance of ImageEnhancer
• Change any divs within the page (which have a class of delayed-image-load) into a transparent GIF using a Base64 encoded string.
  • We set the width & height HTML attributes of the image to the required size
  • We know what size the image needs to be because each div has custom data-attr set server-side to the size of the image
  • We then set a class of image-replace onto each newly created transparent image
• We use a 250ms setTimeout to unblock the UI thread and which calls a function resizeImages which enhances the image-replace images so their source is now set to a URL whe

zenorocha

(function() {
    
    var script,
        scripts = document.getElementsByTagName('script')[0];
        
    function load(url) {
      script = document.createElement('script');
      script.async = true;
      script.src = url;
      scripts.parentNode.insertBefore(script, scripts);