evanw/esbuild

Prefer upstream esbuild unless you specifically need Netlify’s custom downstream behavior. This fork looks like a specialized internal branch with significant drift and no recent maintenance, so it is better as a legacy compatibility choice than a default production dependency.

Choose upstream unless you need this exact snapshot for a local experiment; the fork adds no visible value and is already behind.

Prefer upstream unless you specifically need this fork's custom syntax or parser behavior. This fork looks useful as a legacy or experimental branch, but its age and divergence make it a poor default choice for new adopters.

Choose this fork only if you need its older custom behavior. For most adopters, upstream esbuild is the better default because it is actively maintained and has far more recent fixes and compatibility work.

Prefer the fork only if you need its older, customized parser/CSS behavior and can accept missing recent upstream fixes. For most users, upstream esbuild is the safer choice.

Prefer upstream unless you already depend on this fork's changed defaults or legacy API surface. This fork is best treated as a maintenance snapshot for existing users, not a general-purpose replacement.

Prefer this fork only if you specifically need its older behavior or its custom serve/compatibility patches. For most adopters, upstream is the safer choice because this fork is years behind and likely missing substantial fixes and features.

Choose this fork only if you need its local behavior and are willing to own divergence. For most adopters, upstream esbuild is the safer default because this fork is far behind and appears to have trimmed or replaced significant parts of the standard implementation and test coverage.

Choose this fork only if you need its specific older cache/plugin behavior or legacy compatibility quirks. For most users, upstream esbuild is the better default because this fork is stale, significantly behind, and likely to require ongoing manual repair work.