swc-node VS m3o

swc-node is much faster. No typechecking but you can have that running as a separate process with typescript in watch mode. Basically never have to wait for compiles or typechecking checking then.

fwiw swc has an official loader: https://github.com/swc-project/swc-node

I actually just switched my team's app over to use https://github.com/Brooooooklyn/swc-node for our Jest tests, but if we're going to upgrade to Next 12 it'd be nice to reuse whatever's included there.

I actually upgraded my team's Jest config to use https://github.com/Brooooooklyn/swc-node a few weeks ago. However, our Jenkins CI agents run RHEL7, and neither of the Linux binary targets would run. The `x64-gnu` binary needed a `GLIBC_2_23` symbol when only 2.18 was available, and the `x64-musl` binary had no `musl-libc` on the machine. I don't own the Jenkins agents, so I couldn't install other deps myself.

I ended up building `musl-libc` from source on another RHEL7 agent, committed the `.so` to our repo, and added that to the `LD_LIBRARY_PATH` in our Jenkinsfile, and actually got that working.

I did see some mentions that Rust could build to target an older GLibc ( https://kobzol.github.io/rust/ci/2021/05/07/building-rust-bi... ), so I'm curious if Next is going to use copies of SWC built that way for better compat or if it will require more workarounds on my part.

I'm very curious if the Next SWC binaries

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.