inexorabletash

This demonstrates the implementation of full text search for documents in Indexed DB.

• Word-breaking and stemming is used to create a list of terms for each document.
• Document records are annotated with the list of terms when added to the database.
• A multi-entry index on the list of terms is populated.
• A query is similarly processed into a list of terms.
• A join over the terms is implemented using multiple cursors on the index.

The necessity of annotating records with the word list to populate the index is a limitation of the current Indexed DB API. A feature request to support custom

monokh

const { Token, WETH9, CurrencyAmount, TradeType } = require('@uniswap/sdk-core')
const { Route, Trade, Pair } = require('@uniswap/v2-sdk')
const ethers = require('ethers')

;(async () => {
  const CHAIN_ID = 1
  const daiAddress = '0x6B175474E89094C44Da98b954EedeAC495271d0F'
  const tokenA = WETH9[CHAIN_ID]
  const tokenB = new Token(CHAIN_ID, daiAddress, 18, 'DAI', 'DAI')
  const pairAddress = Pair.getAddress(tokenA, tokenB)

guest271314

Why I use node, deno, bun, qjs, tjs at the same time.

Winds up being a (not the) rather comprehensive JavaScript toolbox. The idea being for the modern JavaScript programmer can use all of the tools available for a given requirement, task or job, without preference for any. No external bundlers or compilers are needed. No frameworks are needed. I can use qjs or tjs for systems with minimal RAM and disk space; and when I want to use Web API's deno makes an effort to provide those interfaces. In some cases I can run the exact same code in bun, deno, and node, which provides a means to perform 1:1 testing as to performance.

There's probably a few things I am unintentionally omitting below. These are just a brief synposis. I'll update accordingly.