m3o VS ts-node

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.

I thought this was going to be a project like ts-node [1]

[1] https://github.com/TypeStrong/ts-node

The command specified in the app option uses ts-node by default, which is an execution engine for Node.js that allows you to run TypeScript code directly. The --prefer-ts-exts flag prevents ts-node from prioritizing precompiled .js files and will always import the TypeScript source code instead, if it is available. This is useful if you are also using tsc (the TypeScript compiler) alongside the app option. The bin/cdk.ts file is the entry point for our CDK app, which defines the main function that will be executed when the app is run.

If you want to write apps that run on Node.js I would suggest using Google’s TypeScript style guide. You can start using it by simply running npx gts init. I’d suggest that you start with this and run your apps using ts-node/ts-node-dev because it does not require an extra build step.

ts-node (“TypeScript execution and REPL for Node.js”)

Here is a relevant discussion and dev comment: https://github.com/TypeStrong/ts-node/issues/155

It does support ESM, with a --loader[1], but even with its SWC option it’s still significantly slower than the esbuild loader I’m working on. Unfortunately, esbuild isn’t totally compatible with tsc, so it’s not a drop-in replacement without plugins.

1: https://github.com/TypeStrong/ts-node#native-ecmascript-modu...

The process of compiling TypeScript source files into JavaScript code before executing them with Node.js can get a little tedious after a while, especially during development. You can eliminate the intermediate steps before running the program through the ts-node CLI to execute .ts files directly. Go ahead and install the ts-node package using the command below:

I tried suggested solution by https://github.com/TypeStrong/ts-node/issues/1007 but this causes problem with NestJS decorators: