Long Ho

SDE @perplexity_ai, TC39 - ECMA402, ex-@CloudKitchens, @Dropbox, @yahoofinance, @iHeartRadio, @Selerity
react-intl/formatjs maintainer

[Long Ho @longlho]

I opensourced a thing https://t.co/E0fULHnmC8
3 - 30x faster than Knip, powered by @OxcProject resolver and rayon

[Long Ho @longlho]

wrote about why “metaframework is dead” feels true rn.

not bc frameworks are useless, but bc @OpenAIDevs Codex + @claudeai Claude Code make explicit scaffolding cheap. i’d rather codegen real routes/contracts than hide more runtime magic.

https://t.co/15U9hDqf9h

[Long Ho @longlho]

A package is a distribution boundary.

Use package names for code that leaves the monorepo. Use root imports for internal source. Enforce architecture with visibility/lint rules, not fake package.json files everywhere.

https://t.co/2Nbdleocqn

[Long Ho @longlho]

Last part is up: a frontend build system is product infrastructure.

@bazelbuild gives you precision, but teams still need rule APIs, codegen, docs, good errors, metrics, and gradual adoption so the graph stays usable.

https://t.co/LG06YLpWFL

[Long Ho @longlho]

Part 7 is up: @bazelbuild, @turborepo , and @NxDevTools are not one ladder.

Turbo runs package tasks. Nx models projects. Bazel models actions and artifacts. The right choice depends on where your repo’s complexity already lives.

https://t.co/IFpGkwlIj7

[Long Ho @longlho]

Part 6 is up: a successful bundle is not the same as a correct artifact.

Use @bazelbuild to verify built outputs, then make deploys consume those verified artifacts instead of rediscovering files from the working tree.

https://t.co/ROyRZrECdY

[Long Ho @longlho]

Part 5 is up: @bazelbuild should not replace Vite.

Bazel decides what the app needs; Vite turns it into a bundle. Apps, SDKs, tests, Storybook, assets, and output checks all become explicit graph edges.

https://t.co/yaqDwHwiLN

[Long Ho @longlho]

Part 4 is up: some frontend inputs are graph questions.

Translations, icons, routes, and generated TS packages get cleaner when @bazelbuild can model them as named artifacts instead of side effects.

https://t.co/KYv1YQYl1t

[Long Ho @longlho]

Part 3 is up: typechecking is not one giant tsc --noEmit.

Split runtime, test, config, generated, and lint contracts so @bazelbuild can catch dependency leaks where they happen.

https://t.co/izDDcsuJbi

[Long Ho @longlho]

Part 2 is up: frontend packages are rarely just TypeScript folders.

This one breaks down runtime code, tests, stories, config, assets, visibility, and codegen as separate build surfaces so @bazelbuild can rebuild less and explain more.

https://t.co/U2dPeVhrLk

[Long Ho @longlho]

Part 1 of my series on @bazelbuild for large frontend monorepos.

At scale, the hard question is not “how do we build the app?” It is “what did this change affect?”

https://t.co/gCW3kCc3HV

[Long Ho @longlho]

@kentcdodds RSC comes with a huge amount of footguns. Literally the 1st thing we did when I joined PPLX.
https://t.co/L3mXvZ9i34

[Long Ho @longlho]

Just wrote a piece a long hiatus https://t.co/DiKE53Pc7o

[Long Ho @longlho]

formatjs, now supporting svelte
Formatter, linter, CLI, the whole thing
https://t.co/OTF5AzFCir

[Perplexity @perplexity_ai]

Introducing Perplexity Computer.

Computer unifies every current AI capability into one system.

It can research, design, code, deploy, and manage any project end-to-end.

[Long Ho @longlho]

@jasonbosco Would formatjs be eligible for Typesense Cloud-sponsored plan?

[Long Ho @longlho]

@jasonbosco does TypeSense offer free plan for OSS projects?

[Long Ho @longlho]

@boshen_c the oxfmt binary on GH release seems to have way less capabilities than oxfmt package on npm. Is that intentional?

[Long Ho @longlho]

@boshen_c So event sourcing basically?

[Long Ho @longlho]

@boshen_c Nice thanks for the fast fix! Btw we just ported our icu messageformat parser to Rust. Is there a way to write custom oxlint in rust or nah?