| 'use client'; | |
| /* | |
| This file is adapted from next-themes to work with tanstack start. | |
| next-themes can be found at https://github.com/pacocoursey/next-themes under the MIT license. | |
| */ | |
| import * as React from 'react'; | |
| interface ValueObject { |
| /** | |
| * Steps to use: | |
| * 1. Create CF Worker, copy and paste this in | |
| * 2. (Optional) Update configuration defaults | |
| * - If you want to manage in code, do so below under "Static Configuration" | |
| * - If you want dynamic custom config: Create CFW KV namespace, link them, and add reference below | |
| * | |
| * - You can overwrite default path prefix for loading analytics.js (<yourdomain>/ajs) | |
| * (corresponding KV entry: `script_path_prefix`) | |
| * - You can overwrite default path prefix for handling first-party data collection (<yourdomain>/data) |
Image.js from the source below (it is almost a copy of Image.js from tiptap-extensions
except that it has a constructor that accepts uploadFunc (function to be called with image being uploaded) and additional logic if(upload) { ... } else { ... previous base64 logic .. } in the new Plugin section.import {Node, Plugin} from 'tiptap'
import {nodeInputRule} from 'tiptap-commands'
/**
* Matches following attributes in Markdown-typed image: [, alt, src, title]
*
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
| """ | |
| A custom type for argparse, to facilitate validation of email addresses. | |
| Inspired by this SO question: http://stackoverflow.com/questions/14665234/argparse-choices-structure-of-allowed-values | |
| and this gist: https://gist.github.com/gurunars/449edbccd0de1449b71524c89d61e1c5 | |
| """ | |
| import re | |
| import argparse | |
I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.
I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.
Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.
These use separate document structures instead of HTML, some are more modular libraries than full editors
| NOTE: This document is OLD - and most of the tips here are probably outdated, since newer versions of Javascript have been | |
| released over the years - with newer optimizations and more emphasis on optimizing newly supported syntax. | |
| // Array literal (= []) is faster than Array constructor (new Array()) | |
| // http://jsperf.com/new-array-vs-literal/15 | |
| var array = []; | |
| // Object literal (={}) is faster than Object constructor (new Object()) | |
| // http://jsperf.com/new-array-vs-literal/26 |
| from pprint import pprint | |
| import jinja2 | |
| import markdown | |
| HTML_TEMPLATE = """{% macro get_html() %} | |
| {{ content | markdown }} | |
| {% endmacro %} | |
| {% set html_content = get_html() %} | |
| Title from Markdown meta-data: {{ get_title() }} |
| from collections import OrderedDict as _OrderedDict | |
| try: | |
| from thread import get_ident as _get_ident | |
| except ImportError: | |
| from dummy_thread import get_ident as _get_ident | |
| class ListDict(_OrderedDict): | |
| def __init__(self, *args, **kwds): | |
| try: |