rviscomi

[web-app-manifest]
const response_bodies = $WPT_BODIES;

const manifestURLs = new Set(Array.from(document.querySelectorAll('link[rel=manifest]')).map(link => {
  const base = new URL(location.href).origin;
  const href = link.getAttribute('href');
  return new URL(href, base).href;
}));

const manifests = response_bodies.filter(har => {

andydavies

document.documentElement.innerHTML = '';

for (const obj of [document, window]) {
    for (const event of Object.values(getEventListeners(obj))) {
        for (const {type, listener, useCapture} of event) {
            obj.removeEventListener(type, listener, useCapture)
        }
    }    
}

andydavies

/* 
 * For more detail see https://andydavies.me/blog/2020/09/22/exploring-site-speed-optimisations-with-webpagetest-and-cloudflare-workers/
 * Started from Pat's example in https://www.slideshare.net/patrickmeenan/getting-the-most-out-of-webpagetest
 *
 * Change site to be site you want to experiment with
 */

const site = 'www.example.com';

async function handleRequest(request) {

erykpiast

# I'm a lame, sorry
FIRST_RUN="true";
function show_aliases_available_for_the_last_command {
    if [[ "$FIRST_RUN" == "true" ]]; then
        FIRST_RUN="false";
        return;
    fi

    local LAST_COMMAND=$(history | tail -1 | cut -d' ' -f2- | xargs);
    local FOUND_ALIASES=$(alias | egrep "^[a-z]+='$LAST_COMMAND .*'$");

jkrems

JavaScript File Format Differences

There's the pervarsive notion that all JS is created equal and that there's only minor and easily detectable differences between the various file formats used to author JavaScript. This is correct, from a certain point of view.

For many people writing JavaScript that gets passed into build tools,

developit

comlinkage

Dynamic import, but where the module you import runs in a different thread.

Powered by Comlink and Module Workers.

Available via unpkg: https://unpkg.com/comlinkage

Usage

developit

Module Worker polyfill for Chrome 61+

Chrome 61+ supports dynamic import() within Classic Workers. We can use this to polyfill Module Workers to a reasonable degree of accuracy.

The only trick is that we need to queue up any messages received while we wait for the module tree to load in the Worker, since Module Workers load the entire dependency graph before flushing messages queued during Worker instantiation.

This polyfill comes in two versions:

module-workers-polyfill-inline.js is a single-file polyfill, but creates Workers with an Opaque Origin. If you're only loading dependencies from absolute URLs and not relying on storage like IndexedDB, this option is fine.

gokulkrishh

NPX (NPM Package Runner) Commands

List of useful npx (NPM Package Runner) commands.

What is NPX?

Using NPX we can execute/run node binaries without the need to install it locally or globally.

Commands

developit

Polyfill dynamic import() in all ES Modules-supporting browsers.

Drop this polyfill into your page: https://github.com/GoogleChromeLabs/dynamic-import-polyfill

... then add the Babel transform:

import dynamicImportPolyfill from 'dynamic-import-polyfill';

zkochan

{
  "scripts": {
    "preinstall": "node --eval \"!process.env.npm_config_user_agent.startsWith('pnpm/')&&(console.log('Use `pnpm install` to install dependencies in this repository')||true)&&process.exit(1)\""
  }
}