pext.dev @PextDev

We automatically transpile your entire PHP codebase into a JavaScript application statement by statement. No manual rewrites or migration headaches. pext.dev Joined April 2026

Tweets

30
Followers

38
Following

372
Likes

16

pext.dev @PextDev

2 weeks ago

@matteocollina shipping on the same topic (php to node). nice to see popularity in rewriting stuff prom one language to another :)

0 0 0 605 0

View Details

pext.dev @PextDev

2 weeks ago

Leaving PHP, Part 3: the type system arrived late and incomplete pext.dev/blog/leaving-p…

0 0 1 29 0

View Details

pext.dev @PextDev

2 weeks ago

Transpiling dragonmantank/cron-expression from PHP to JS: timezones, DST, PHP date formats, and a cache for Intl.DateTimeFormat pext.dev/blog/cron-expr…

0 0 0 35 0

View Details

pext.dev @PextDev

3 weeks ago

@JLarky what if instead of rewritten is transpiled: LaravelJS

0 0 0 547 0

View Details

@developedbyjosh @laravelphp @vuejs @inertiajs @nuxt_js I would tend to think that Laravel community people already move away little by little when adopting anything new with a trailing js in its name :)

1 0 1 48 0

View Details

pext.dev @PextDev

4 weeks ago

@developedbyjosh @laravelphp @vuejs @inertiajs @nuxt_js Looks solid. Curious how teams using setups like this think about the long-term path, staying on Laravel forever or eventually moving the backend to Node to be on JS E2E.

2 0 1 79 0

View Details

pext.dev @PextDev

4 weeks ago

Transpiling composer/semver: PHPUnit 9 via Symfony symlink and eval-generated version_compare pext.dev/blog/semver-co…

0 0 1 79 0

View Details

pext.dev @PextDev

4 weeks ago

Part 1 looked at the people you can hire to write PHP. Part 2 looks at the architecture they would inherit on day one. PHP's defining choice, shared-nothing process-per-request, was the right answer for the 2005 web. In 2026 it is a structural tax that the rest of the stack has stopped paying. pext.dev/blog/leaving-p…

0 0 1 82 0

View Details

pext.dev @PextDev

4 weeks ago

A recap of what shipped during the week of 27 April. Six items this week: a complete audit of the math module against every PHP version since 4, two more Pure Utilities packages converted at 100%, a deep analysis of string literal encodings, an experimental TypeScript output mode in the transpiler, and initial support for static variables inside functions. pext.dev/blog/week-in-r…

0 0 0 66 0

View Details

pext.dev @PextDev

4 weeks ago

Full writeup with the comparison table (Pext vs AI vs manual rewrite, including the lock-in question): pext.dev/blog/pext-vs-a…

0 0 0 24 0

View Details

pext.dev @PextDev

4 weeks ago

The mental model: • Migration = mechanical, must be correct, deterministic transpiler • Improvement = creative, can be iterative, AI Using AI for migration is asking it to do the hard part without the foundation. Using it for improvement is using it where it’s strongest.

1 0 0 33 0

View Details

pext.dev @PextDev

4 weeks ago

Everyone asks if AI killed our PHP-to-JS transpiler. Wrong question. AI can’t migrate a PHP codebase. Not because it’s not smart enough, because it’s solving the wrong problem. Here’s what we learned building Pext for 3 years

1 0 0 49 0

View Details

pext.dev @PextDev

4 weeks ago

Pext's math module reached full PHP parity this week. That label means something specific: every public function, every constant, the new RoundingMode enum, on every PHP version from 4 forward, with every documented edge case checked. The road there ran through the gaps between JavaScript's Math, IEEE 754, C99, and twenty years of PHP compatibility decisions. This post walks through the parts worth knowing about. pext.dev/blog/math-modu…