token-lists VS esbuild

Uniswap tokenlist format

We’re thrilled to announce that the Crypto.com DeFi Wallet has integrated Token Lists!

I know that in order to get the addresses of every ERC20 token, https://etherscan.io/ and https://tokenlists.org/ are the way to go.

It's important to note that Uniswap is decentralized and anyone can "list" anything for trading without asking anyone or going through any process. This means there are thousands of tokens, probably millions in the future, available to trade.

Users do not see these tokens unless they actively search them out. Uniswap uses the TokenList standard (https://tokenlists.org/) and by default users only see tokens such as the top 100 projects on CoinGecko. There are many lists created by reputable players such as Aave and Gemini which cover the entire gamut of projects users want to trade without exposing end users to scam tokens.

I believe this is a good system and has worked well as having any kind of listing process or even a DAO introduces subjectivity and provides points of capture for bad actors. With an open listing process and standards like TokenLists we can say that Uniswap is truly a public good and will be around as long as we need it which provides a guaranteed way to swap any asset for any other asset no matter who created it or how controversial it is which is a good primitive for humanity to be able to rely on.

This should get you there.

During my search for deploying Lambdas via GitHub actions, I came across a tutorial that utilized ncc for converting TypeScript and bundling. While ncc is effective, I discovered esbuild, which proved to be significantly faster and perfectly suited to my requirements.

The advent of esbuild, the native support for ES Modules in browsers, the widespread adoption of import map, the emergence of tools like Native Federation, and the Nx ecosystem all combine to forge a flexible and well-maintained Micro Frontend Architecture.

EsBuild is a relatively new, blazing-fast JavaScript bundler and minifier. It stands out for its high performance, significantly speeding up the build process in development pipelines.

Unlike Webpack, the Vite DevServer only compiles files when they are requested. It leverages ES module imports, which allow JS files to import other files without needing to bundle them together during development. When one file changes, only that file needs to be re-compiled, and the rest can remain unchanged. Project files are compiled with Rollup.js. Third-party dependencies in node_modules are pre-compiled using the ultra-fast esbuild bundler for maximum speed, and they are cached until the dependency version changes. Vite also provides a client script for hot module reloading.

Use esbuild to build the React code into a form executable on both the server and client sides.

The functions will bundle using esbuild. For that, it is required to install esbuild globally:

TSX is the newest and most improved version of our ts-node, using ESBuild to transpile TS files to JS very quickly. The most interesting part is that TSX was developed to be a complete replacement for Node, so you can actually use TSX as a TypeScript REPL, if you install it globally with npm i -g tsx, just run tsx in your terminal and you can write TSX natively. But what's even cooler is that you can load TSX for all TypeScript files using --loader tsx when you run your file. For example, let's say we have this file called index.ts:

esbuild plus Vite is out of developer preview and enabled by default, yielding 67%, 87%, 80% speed improvements for build time, hybrid build time and hybrid serve time respectively.

Bundling with esbuild

Besides Webpack, there are many other popular web bundlers available, such as Parcel, Esbuild, Rollup, and more. They all have their own unique features and strengths, and you should make your decision based on the needs and requirements of your specific project. Please refer to their official websites for details.