Now for the columns! What mcu are you using?

"...learning to operate a textile loom in 1820"

❤️

Oof. Extra nightmarish if you're putting together a monorepo.

I think the trick is to get the TS language server as well as a bundler and Node happy with the setup.

I like some kind of combination of TS project references and conditional package exports.

colinhacks.com/essays/live-...

moonrepo.dev/docs/guides/...

😔

If you're working with a monorepo type thing then tsBuildInfo might help?
www.typescriptlang.org/tsconfig/#ts...

There are quite a few JS/TS kernels for Jupyter Notebooks.

github.com/jupyter/jupy...

That tracks. Especially considering the impact LLM's are having on writing code.

Do you think it's because of the complexity of modern web-apps? Will the needle swing back as our abstractions mature?

I think it's frowned upon because it strays too far from plain JS. The line being: If we were to replace all the type annotations with whitespace, will it still work?

Perhaps using a global error page would do the trick?
nextjs.org/docs/app/bui...

lol. No worries.

What? This isn't related to TypeScript! i've been duped!

Have you tried the Vitest VSCode extension? Dunno if I'm just lucky but debugging tests just worked out of the box!

Losing it? Did they ever have it?

That's interesting - did you reach for a custom adapter in better-auth?

Quick question: what sets better-auth apart for you?

I get the feeling the industry is still working on standardising what constitutes an Agent.

Anthropic seems to make a distinction between Agents and Workflows: www.anthropic.com/research/bui...

It kinda makes me think that agents are self-directed; they involve an LLM in choosing what to do next

Oh that sounds interesting- I'll take a look

Ooh. What's the plan to avoid the suckyness?

DHH (the Rails guy) was espousing the same idea a few years ago - I'd like to think it helped shift the Overton window in favour of SSR.

Array.prototype.reduce gets quite close: The callback's 3rd arg is the index. Return the accumulator and the current value spreaded to flatten.

Eg.

[[1], [2,2], [3,3,3]].reduce((acc, curr, idx) => idx > 1 ? [...acc, ...curr] : acc, [])

I'd argue chaining filter and flatMap is usually clearer tho

🦆 If it quacks like a duck...

About completeness: yeah, this only handles type-annotations. Enums and the like are behind another flag. Node is also waiting for the JS decorators proposal to land before adding support for them.

My take: prefer safeParse when using TS.

Form validation failing isn't exceptional - it's a thing that can (and probably should) be modelled using the type-system.

Caught errors are of type `any` - using that for flow control is a shlep.

It's such a good extension! Makes VSCode feel like real IDE!

Also:
- type annotations get replaced with whitespace
- remember to `import type` else node tries to import types that it replaced with whitespace
- debugging works well enough
- don't mix esm and cjs imports
- tsx not supported
- path aliases not supported

Ran into this. Thought you might be interested:
www.aihero.dev/evalite-an-e...

I've also been having this fight myself. This was quite useful: moonrepo.dev/docs/guides/...

Ah - LangSmith and LangFlow might help there, though they don't really focus on doing things locally.