← Feed

Posts

• View post

  just supported @kimai with a drive-by #phpstan improvement for their GitHub Actions pipeline status quo was: 66s after disabling pcov: 53s after update to PHP8.3 - which enables PHPStan turbo: 34s with persistent and warm result-cache: 4s https://github.com/kimai/kimai/pull/6183

• View post

  After my summer break I am back at my primary job. Started updating #phpstan in our closed source projects CI. one example: PHPStan 2.2.5: 70s PHPStan 2.2.14: 37s nice to see our recent #performance focus pays off in real world projects 🚀

• View post

  #phpstan recently started erroring about assertEmpty() and assertNotEmpty() #PHPUnit assertions, when phpstan-strict-rules are enabled (because these forbidd empty()). Just released autofixers for phpstan-phpunit for the most common cases.

• View post

  #phpstan 2.3.x added new dependency tracking APIs which allow custom extensions/rules to declare values/files they depend on. todays #phpstandba 0.5 release uses the new APIs, which allows us to re-analyze only code depending on the database schema when it changes.

• View post

  anyone using the #composer/#xdebug-handler and want to give this PR a try? the idea/question is, whether/when pcntl_exec is more efficient than running/wiring up a subprocess would be great this could be tested in more applications https://github.com/composer/xdebug-handler/pull/176

• View post

  For the best experience you should install #phpstan using #composer! when downloading the phpstan.phar with curl/wget or via package managers like e.g. homebrew or phive, chances are high you will miss necessary PHPStan Turbo files. Analysis will be a lot slower without Turbo!

• View post

  fasten your seat belt - #phpstan 2.3.x will be a another massive step forward 🥳 we are not yet ready with it though 🤡

• View post

  see you on #phpdd next week in dresden?

• View post

  running different #PHPStan versions on #shopware 6 2.1.43: 1m 33s - takes 8.79GB memory 2.2.8: 1m 25s - takes 7,46 GB memory

• View post

  Anyone out there with a open source codebase, running #phpstan in CI takes more than 5 minutes? I would love looking into what makes it slow for you Send me a link to your CI logs RT

• View post

  @OndrejMirtes@phpc.social handed me over a list of #php-src commits to verify and contribute to the php runtime. So I started opening pull requests on the php project to improve performance of #phpstan. Lets see how it goes - wish me luck :-)

• View post

  Last week I had an idea on how we can improve efficency when #phpstan needs to work with big unions of constant types (e.g. enum with lots of caes). this had a nice impact on some example of our benchmark suite

• View post

  Since April 2026 we fixed ~280 issues on #phpstan. We implemented lots of new features and improvements along the way and made it even faster at the same time. be prepared for the next release which will do another big leap in #performance 🚀

• View post

  In case you think #phpstan is running too slow, have a look at the result of running `phpstan analyze` command with `-vv` and check whether it utilizes the result cache When the result cache is warm, it should be wicked fast in CI you likely need to persist the cache manually see https://phpstan.org/user-guide/result-cache#setup-in-continuous-integration

• View post

  #phpstan 2.2.3+ is able to detect package updates based on composer.lock. utilizing the pre-existing dependency graph, we need to re-analyze only affected files. Previously we had todo a full project analysis. contributed by @sander_scode

• View post

  We have a few really cool perf experiments running atm to get #phpstan even faster.. some of them look really promising. 🫰

• View post

  contributed to #phpstan by @zonuexe@phpc.social: PHPStan will have a better idea about purity of callables taking a callback argument. for example will `array_map($pureCb, $arr)` be considered pure: - less false positives - better dead code detection

• View post

  @OndrejMirtes had another great idea to speedup #phpstan analysis Implementing it was easier than expected :-)

• View post

  In case your daily #phpstan run takes minutes instead of seconds you likely don’t utilize the result cache. Find solutions at https://staabm.github.io/2023/10/21/phpstan-result-cache-gotchas.html

• View post

  Recently I learned that the order in which you pass options to a CLI command can have a huge perf impact on the runtime (even if it leads the same result)

• View post

  dumdidum.. 🚀 #phpstan

• View post

  yesterdays #phpstan 2.1.43 release fixes 37 issues. this means since 2.1.40 (released ~4 weeks ago) we fixed ~195 issues. fingers crossed we can keep the pace and reach our goal of pushing open issues to < 1000 in the upcoming months.

• View post

  my non-scientific benchmark suggests running #PHPStan on #wordpress core, will be a lot faster starting with the next release

• View post

  It was a pleasure to work with @misterdeviling thru a lot of old #PHPStan bugs. Yesterdays release contains a massive package of fixes. while we concentrated on the maintenance parts, @OndrejMirtes could concentrate his efforts on improving DX with better docs and other nice additions.

• View post

  Achievement unlocked: crossed the 1000 commits line in @phpstan core

• View post

  I recently learned that git bisect has a "run" subcommand, which allows you to automate the bisect process. in a blog post I am describing how you can find a regression commit in phpstan-src. the same approach works for any git based project. https://staabm.github.io/2026/02/07/git-bisect-run.html

• View post

  Starting with #phpstan 2.1.39 in case we know constants are deprecated only in certain php versions, we no longer error about them, when used in a `if (PHP_VERSION_ID < 80400) {`-like condition. see E_STRICT before PHP 8.4: https://phpstan.org/r/0dc9fe34-0c60-4254-9174-f37e910cb4cf

• View post

  I love solving puzzles.. today I found out that a #phpstan container cache invalidates when you resize your bash/shell window. also when jumping between directories using `cd`. not intentional of course. lets see what we can do about that.

• View post

  TIL: your github action might fail because of a overlong command line, which gets cut without further notice. Not sure its a #php or #windows or #githubactions effect. 1:1 the same command works on a ubuntu based github action without error

• View post

  @Tideways@phpc.social congratulations 🎉