← Feed

Posts

• Post #4133048

  Announcing PHPStan Turbo! Native PHP extension (PHP 8.3+) written in C++ that makes running PHPStan 10-30 % faster. The best part: If you update to PHPStan 2.2.6, you get it automatically. It ships with pre-built binaries for all the usual combos of OS:architecture:PHP.

• Post #4118622

  Hot take: thanks to LLM coding agents, the average software quality will increase, not decrease.

• Post #4063359

  Embarking on a vision quest for the next major PHPStan feature.

• Post #3551347

  PHPStan 2.2.4 addresses the RAMpocalypse! It now consumes a lot less memory. See for yourself by running "analyse -v". Running PHPStan itself used to consume 2,8 GB, now it consumes 2,1 GB. On a big real-world project, the consumption went down from 17,45 GB to 14,1 GB.

• Post #3056504

  Goodbye PHPStan 2.1.x 👋 It's been nice 18 months. https://github.com/phpstan/phpstan/releases/tag/2.1.56 Now onto PHPStan 2.2.0. It's coming on Thursday.

• Post #3056503

  PHPStan 2.2: Unsealed Array Shapes, Safer Array Keys, and More! https://phpstan.org/blog/phpstan-2-2-unsealed-array-shapes-safer-array-keys

• Post #2539128

  My opinion on the latest Bound-Erased Generic Types RFC: https://externals.io/message/130816#130853 (spoiler alert: I like it)

• Post #2539127

  WebExpo Prague is happening again in two weeks, and I wouldn't miss it. It's one of the best places to meet software people from across the scene in one place. Use MIRTES26 for 1 000 Kč off at webexpo.net. See you there!

• Post #1169360

  I love git bisect and I wanted PHPStan to have its own bisect command. So I made it. If PHPStan reports a bug in your code but you know it's wrong and that it used to work before you upgraded, you can use bisect to pinpoint the exact commit where the behaviour changed. Available now in 2.1.47!

• Post #984480

  I’m trying to wrap my head around the fact that 10-15 years ago Linux was the OS with the worst UX, now it’s the one with the best UX. Because it’s made by volunteers who only care about the result and their users, but Microsoft and Apple mostly care only about themselves.

• Post #984479

  RE: https://phpc.social/@nicwortel/116328298481899621 Can’t wait to delete all that object-oriented pesky typesystem code from PHPStan!

• Post #984477

  Something I didn’t have on my bingo card for 2026: a new major version of the only frontend framework I ever learnt and used: Knockout.JS https://tko.io/3to4/

• Post #961707

  Yo dawg, I heard you like comments, so I put comments in your comments, so you can comment while you comment. Now available in phpstan/phpdoc parser 2.1.0 & PHPStan 2.1.6.

• Post #859017

  Come see me at 13:30 in Pathé 1 play Red Alert 2…. uhh, talk about generics in PHP. #dpc26 @dpcon

• Post #859016

  I had a bad hair day at PHP UK but I think this talk recording is still worth your time.

• Post #789621

  Coming soon to the PHPStan playground 💅

• Post #789620

  Using PHPStan to Extract Data About Your Codebase https://phpstan.org/blog/using-phpstan-to-extract-data-about-your-codebase

• Post #746809

  Why Array String Keys Are Not Type-Safe in PHP And What Will PHPStan Do About It: https://phpstan.org/blog/why-array-string-keys-are-not-type-safe

• Post #746807

  New errors are coming to PHPStan:

• Post #606997

  I’m gonna prompt inject the agents myself 😈

• Post #606996

  Several times a week I tell people their problem can be solved by adding @​phpstan-impure above their non-void function (or by setting rememberPossiblyImpureFunctionValues: false). Finally, PHPStan will tell them by itself:

• Post #606994

  For the longest time I was bothered that “Documentation” link on phpstan.org led directly to “Getting Started” page, and that some really useful docs pages weren’t discoverable at all. That changes today. Documentation now has a dashboard with boxes describing what use-case/problem the linked page solves.

• Post #606993

  Error identifiers documentation is finally useful! Take a while and browse everything PHPStan can report: https://phpstan.org/error-identifiers

• Post #390515

  I will be at PHP UK 2026 next month! Showing you how to write custom PHPStan rules, and also trying a new thing: I’ll be in the hallway ready to pair-program with you on your own codebase during PHPStan Office Hours! Use code PHPUK26 for 10 % off the ticket if you plan to go.

• Post #390513

  PHPStan 2.1.34 is out with two great advancements: Optimized performance: between 25 % to 40 % faster times thanks to more caching and raw performance tweaks in code. More precise analysis with Fibers (super-cool) on PHP 8.1+. Upgrade today and let me know how it works for you!

• Post #390507

  Today is a big day and a big step for PHPStan: for the first time ever, I’m not the only person with merge rights on the repository. Two of the most active contributors, @markusstaab and @misterdeviling can also merge PRs!

• Post #390506

  PHPStan fully supports PHP 8.5! https://phpstan.org/blog/phpstan-fully-supports-php-8-5

• Post #390505

  PHPStan Pro just gained filtering errors by identifier! Huge thanks to @sebastian for the idea!

• Post #390500

  Only 12 days after 2.1.39, PHPStan 2.1.40 is out now with 71 fixed issues! 🎉