m3o VS esbuild

Sorry what I meant is I've been working on the open source Micro project for 8 years which underpins this. The chat app itself was not really something I meant as being open source but yes it's in a separate repo with the API hosting product I built called M3O.com.

https://github.com/m3o/m3o

Email: [email protected]

Spent the last 10 years mostly working with microservices and Go based startups, although I would not recommend microservices to most companies. I can save you a few million dollars if you wonder why.

I'm most passionate about improving DevEx in companies. Things like writing custom ORMs for lesser known/supported databases (see eg. https://github.com/gocassa/gocassa). Mostly worked with startups from $2M-$500M funding range, with the occasional enterprise gig.

Used to run a chicken shop as a hobby project which made me careful of accepting management positions, haha, people are hard. I would love to be a product owner, I mostly designed the https://m3o.com/ product with the CEO recently and implemented the MVP of it. It's open source stuff, check it out https://github.com/m3o

Currently working for a US startup but my contract is ending soon.

Cheers!

It's like API indexing, I like it. I started M3O (https://m3o.com) with this idea of API aggregation for absolutely everything but not specifically indexing, more so providing a uniform access layer to all things with one API token. The programmability of Nango will definitely a be a selling point. For the founders, focus on that, double down on that. The ability to program the APIs and the data retrieved is really key.

What if any is the relationship between https://m3o.com/ and https://micro.dev/ ?

Nocode poses a really interesting movement towards rapid prototyping end user facing apps but I think when it comes to functionality, there's always some need to drop into the escape hatch to make that API call or manipulate some javascript. I've been noticing more people using https://m3o.com for that especially with things like Adalo. There's 70+ APIs that can be used with one API token. Super useful. Also on the lookout for other API providers who make it easier to embed those apis.

We can potentially do this on https://m3o.com. It doesn't exist yet but would make sense as the next service we offer. Further details would be useful e.g endpoints required.

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.