PHP - BlogFlock

Your JetBrains IDE Expertise, Now on LinkedIn - PhpStorm : The IDE that empowers PHP developers | The JetBrains Blog

2026-06-17T13:11:02.000Z

Every developer has tools they rely on daily. The workflows they’ve built around them, the ways they’ve learned to move faster, debug smarter, and write better code – that kind of hands-on experience can be hard to put into words.

We’re collaborating with LinkedIn to make it easier for you to showcase your expertise with JetBrains IDEs on the world’s largest professional network. You can now connect your IDE to LinkedIn and let your real tool usage speak for itself.

Connect your IDE

IntelliJ IDEA, PyCharm, WebStorm, PhpStorm, Rider, GoLand, CLion, RustRover, and RubyMine are already supported via a free plugin, while support for DataGrip is coming soon.

In this blog post, we’ll explain what LinkedIn connected apps are, what they mean for your profile, and how to get started.

What this is about

Building on early collaboration with Descript, Duolingo, Lovable, Relay.app, and Replit, LinkedIn is expanding the range of apps you can feature on your LinkedIn profile, turning real-world product usage into a credible, visible signal of practical tool experience. We’re glad to join forces with them to bring this to JetBrains IDE users.

“We’re building new ways for members to show real, credible proof of what they’re capable of, right on their LinkedIn profile. And for the brands behind these tools, there’s no better endorsement than a customer who’s actively using and loving your product.”
– Dan Shapero, CEO of LinkedIn

Connected apps let you link the tools you use in your daily work directly to your LinkedIn profile, where they appear prominently, helping you stand out to your professional network. Once connected, each app generates a simple statement based on how you actually use it. Unlike manually added skills, this is based on real usage and updates automatically as your experience evolves.

How to get started

Open your JetBrains IDE, go to Settings | Plugins, search for the LinkedIn Connected Apps plugin under the Marketplace tab, and install it.

Once installed, the plugin starts collecting data locally about how you use your IDE. Depending on your usage history, you may receive an initial statement right away, which will then be updated once the plugin has collected enough data to better reflect your real IDE expertise.

Your IDE usage data stays on your machine. When you are ready, you can connect your LinkedIn account and share your IDE expertise badge there. If you keep the plugin installed, your badge will update automatically as your IDE usage evolves.

The plugin is free for all JetBrains IDE users.

What’s included in this release

This is the first version of the integration, delivered as a standalone plugin rather than being built directly into the IDE. It covers IntelliJ IDEA, PyCharm, WebStorm, GoLand, PhpStorm, Rider, CLion, RustRover, and RubyMine; DataGrip is not yet supported.

Usage is detected within the IDE itself, so if you use AI features via an external tool or terminal, those won’t be reflected yet.

How your IDE expertise is determined

The model is intentionally simple for now. It is designed to represent your practical use of JetBrains tools, not to rank developers or certify skill levels. Our goal was to provide a solid starting point, but we know there’s more to capture about how developers work with their IDEs.

Statements map to different levels of experience and are generated based on how you interact with your IDE – from writing and editing code using basic features to working with debugging tools, version control, and AI-assisted workflows. For more information, see our documentation.

What’s coming next

We’re already working on the next version, planned for later this year. We’ll focus on improving how IDE usage, including AI feature usage, is represented, expanding support to DataGrip, and making the overall experience feel more integrated.

FAQ

Which JetBrains IDEs are supported?

IntelliJ IDEA, PyCharm, WebStorm, GoLand, PhpStorm, Rider, CLion, RustRover, and RubyMine. Support for DataGrip is coming soon.

Why isn’t DataGrip supported yet?

DataGrip is designed for working with databases and includes workflows that differ from our other IDEs. We plan to support it soon.

Can I connect multiple IDEs?

Yes, if you use multiple supported JetBrains IDEs, you can connect each of them. You’ll get a badge for all connected IDEs.

Note: If you use multiple JetBrains accounts across different IDE instances but link them all to the same LinkedIn profile, IDE usage statements from each account will be displayed on that LinkedIn profile.

Do I need to keep the plugin installed after connecting?

You can share your IDE usage statement once and then remove the plugin, but note that it must remain installed if you want to track your ongoing progress and have any changes reflected on LinkedIn.

Is this feature free?

Yes, it’s available to all JetBrains IDE users at no cost.

Is this a certification?

Connected apps reflect real IDE usage and are designed to showcase applied experience, not to act as a formal certification or skill ranking. Certifications, degrees, and licenses remain important markers of professional achievement. Connected apps on LinkedIn add a different kind of signal: partner-validated tool usage that reflects practical work and can update over time.

What data is shared with LinkedIn and JetBrains?

Only the information required to represent your connected account and IDE usage statement.

Will this help me get hired?

Having connected apps on your LinkedIn profile is extra proof of your practical experience with leading tools. While connected apps make your expertise visible, they are just one part of your profile. Think of it as a way to let your tooling speak for itself.

Give it a try and let us know what you think in the comments below. We’re continuing to develop this integration, and your feedback will help shape what comes next.

Contribute to the State of PHP Survey - PhpStorm : The IDE that empowers PHP developers | The JetBrains Blog

2026-06-11T10:38:57.000Z

Together with The PHP Foundation, we’re embarking on an exciting expedition – the first annual State of PHP census that aims to tally the elePHPant population across the world. Come join us!

Take the survey

With the help of the community, we’ve designed a comprehensive survey that aims to unearth the PHP developer trends – from years of experience and favorite frameworks to AI preferences and beyond. Our goal is to draw the most representative picture of the PHP ecosystem and the developers behind it, and share insights that will benefit the community and help shape the future direction of PHP.

For this to be a success, we need your help. Our survey will only be truly representative if PHP developers of all backgrounds participate, regardless of where you live, how long you’ve been developing in PHP, what frameworks you prefer, or the tools you use. So take part in the State of PHP survey now and help us map the herd!

Survey participants can enter a drawing to win one of five EUR 500 (or equivalent in local currency) vouchers, which they can redeem for any prize they want via Tremendous (subject to the applicable terms and conditions).

State of PHP report

You can expect to read the travel logs from this journey in October 2026. We will publish the aggregated results in the State of PHP 2026 report, so be sure to follow The PHP Foundation and PhpStorm on X or sign up for our newsletter below to be among the first to see the results.

Thank you for being part of the first edition of the State of PHP!

The PHP Foundation and PhpStorm teams

Fixing two minor git irritations in my OSS fork workflow - Rob Allen

2026-05-26T10:00:00.000Z

For OSS work, I work with two git remotes:

upstream: the canonical OSS project repository, where main is the default branch and is what gets released.
origin: a personal fork. All my feature branches live here.

I set up locally like this:

Fork the project repo to my account.
Clone my fork locally, so the origin remote is my fork.
Set an upstream remote using git remote add upstream <ssh-url>.

and then when working on something, I tend to do these steps:

Switch to the main branch with git switch main.
git pull from upstream to pick up the latest code.
Create a new feature branch from main using git switch -c <branch>.
Do work, then commit and push the feature branch to origin.
Open a PR from origin/<branch> against upstream/main (usually using gh).
Once merged upstream, pull from upstream back into my local main branch and delete my feature branch.

The problems

I have a couple of little irritations with this workflow that I finally sat down to solve.

Firstly, when I git pull on main, it pulls from origin by default unless I remember to use git pull upstream main. If I don't catch it, I don't have the latest code when I branch for my new work.
Secondly, when I push my new branch, I get an error message fatal: The current branch foo has no upstream branch which is just irritating as I then sigh and re-run the push with -u origin.

The solutions

To remove these minor irritations, I discovered that I can run these useful git commands:

Firstly, set main to track upstream/main:

git branch --set-upstream-to upstream/main main

Usually I set which repo's branch to track using git push -u, but that doesn't make sense for the main branch as I never push it to the upstream repo. Using --set-upstream-to on the branch command does the same thing, without a push.

Secondly, to make the first git push automatically create the origin/<branch> and track it:

git config push.autoSetupRemote true

Now git pull on main always pulls from upstream, and git push on a new branch just works.

Improving Accessibility in JetBrains IDEs: What’s New and What’s Next in 2026 - PhpStorm : The IDE that empowers PHP developers | The JetBrains Blog

2026-05-21T06:45:13.000Z

Making software accessible often comes down to removing small but repeated points of friction in everyday workflows. Today, on Global Accessibility Awareness Day, we’re sharing recent improvements in JetBrains IDEs across several areas: compatibility with assistive technologies on various platforms, keyboard navigation, and non-visual feedback. Some of these improvements are already available, and some are coming later this year.

You can use the audio player below to listen to this blog post.

Accessibility Blog Post Audio

Better compatibility with assistive technologies

One of the key areas we’ve been working on is improving how JetBrains IDEs interact with OS-level accessibility tools.

Improved Magnifier support on Windows

Screen magnifiers are among the most commonly used assistive technologies in JetBrains IDEs. Until recently, the built-in Windows Magnifier didn’t reliably follow the text cursor in the editor, making navigation and editing more difficult for low-vision users. We’ve implemented support for cursor tracking so Magnifier follows text as you type, just as it does in other applications.

This builds on earlier work on macOS, where we addressed text cursor tracking with macOS Zoom. Now, the same support is being extended to Windows.

Orca and GNOME Magnifier support on Linux

With version 2026.2, coming this summer, JetBrains IDEs will allow you to use the Orca screen reader and GNOME Magnifier in supported Linux environments.

This is an active area of work, with multiple related tasks already underway. Accessibility shouldn’t depend on your operating system, and we’re continuing to improve support across platforms.

More predictable keyboard navigation

We’ve also been making it easier to move through the IDE without relying on a mouse.

Main menu access with Alt on Windows

In native Windows applications, pressing Alt moves the focus to the main menu, allowing you to navigate it with the keyboard. This behavior was previously missing from JetBrains IDEs, and screen readers, such as NVDA, would sometimes announce the system menu instead.

Now, the main menu behaves in a way that feels familiar and predictable for keyboard-only and screen-reader users, and the bright focus indicator helps low-vision users identify the selected item.

Navigating between major parts of the IDE

Another focus area is the experience of moving between different parts of the IDE interface, such as toolbars, panels, and the editor. We’re working on a more structured model for navigating through the big component groups:

Tab and Shift+Tab move the focus within the current area.
A dedicated shortcut lets you jump between larger sections of the IDE.

This reduces the effort required to reach essential controls and makes the overall layout easier to navigate. For the current iteration, we made it possible to bring the main toolbar and status bar into focus, and we fixed the Project and Git toolbar widgets, which were not selectable by screen readers, even though other elements already were.

As the next step, we’ll polish specific controls and include tool window bars on both sides of the IDE frame in the navigation flow.

Exploring richer non-visual feedback with audio cues

Accessibility is not only about reaching controls, but also about understanding what’s happening while you work. We’re exploring ways to provide richer audio feedback in the IDE. Two directions we’re currently investigating:

Contextual signals when the caret lands on lines with errors, warnings, breakpoints, or version control changes. We want the IDE to provide immediate, non-visual feedback in context.
More general audio notifications for IDE actions and state changes.

The goal is to reduce the need to rely on visual indicators or switch contexts just to understand what changed. Instead, we want the IDE to provide that information more directly.

Accessibility as an ongoing effort

We’re improving accessibility in JetBrains IDEs across multiple areas at once, including by providing compatibility with assistive technologies like screen readers and magnifiers, as well as by offering more consistent keyboard navigation and clearer feedback for events that are otherwise mostly visual.

These improvements build on earlier updates, such as support for VoiceOver and NVDA, a high-contrast UI theme, and color schemes for red-green vision deficiency. There’s still more to do, and we’ll continue working in this direction.

We’d love to hear from you

We’re eager to hear from developers who rely on accessibility features, as well as from anyone interested in improving the experience of using them.

If you have ideas or feedback about accessibility in JetBrains IDEs, you can reach us directly at accessibility@jetbrains.com. You can also report issues through YouTrack or the support request form.

If you’d like to stay informed about accessibility improvements, you can subscribe to updates here.

PhpStorm 2026.2 Early Access Program Has Started - PhpStorm : The IDE that empowers PHP developers | The JetBrains Blog

2026-05-12T13:36:37.000Z

The Early Access Program (EAP) for the next major PhpStorm 2026.2 release is now open!

PhpStorm’s EAP builds are a great opportunity to try upcoming features for free in your real workflows and share feedback with the PhpStorm team. Your input directly influences what makes it into the final release.

This release, our main areas of focus are:

Native mode for remote development scenarios, as we aim to significantly improve interaction with the projects located on WSL 2 and in Dev Containers.
Ongoing enhancements in PhpStorm’s understanding of PHPDoc-based generics.
Overall performance and stability improvements, including reduced startup time, indexing time, and freezes.

Download PhpStorm 2026.2 EAP

Getting started with the EAP

If you’re not familiar with how our Early Access Program (EAP) works, here’s a quick overview:

We release new EAP builds weekly, giving you a sneak peek at upcoming features.
EAP builds are completely free to use and do not require a license.
You can install the EAP version alongside your stable PhpStorm installation, so there’s no need to uninstall your current version.
The most convenient way to access EAP builds and keep both your stable and EAP versions up-to-date is by using our Toolbox App.
Alternatively, you can download EAP builds from the EAP page or set up your IDE to automatically receive updates by selecting Check IDE Updates for the Early Access Program under Settings/Preferences | Appearance & Behavior | System Settings | Updates.

Determining if a reboot is required on Linux - Blog entries :: mwop.net

2026-05-04T13:35:08.000Z

I've been using the construct sudo run-parts /etc/update-motd.d/ to determine if recent system updates required a reboot.

Today I learned I can simply check for the existence of the file /var/run/reboot-required.

Determining if a reboot is required on Linux was originally published 4 May 2026 on https://mwop.net by Matthew Weier O'Phinney.

Join Us for PHPverse 2026 on June 9 - PhpStorm : The IDE that empowers PHP developers | The JetBrains Blog

2026-04-30T15:10:32.000Z

JetBrains PHPverse – a community-inspired professional event for PHP developers – returns once more on June 9, 2026. This year, we’re gathering some of the most influential voices in the PHP ecosystem to share their insights on shaping the modern PHP language, the internals of ecosystem tools and frameworks, and the adoption of agentic workflows for shipping PHP code.

About PHPverse 2026

Expect a one-day event of curated talks, live Q&As with the speakers, several special announcements, and even a few surprises (after all, it’s PHP’s 31st birthday).

When: 11:00 am – 3:50 pm UTC on June 9, 2026.

Where: Streamed live on the PHP Annotated YouTube channel.

Hosted by: Brent Roose, JetBrains Developer Advocate for PhpStorm and creator of the PHP Annotated YouTube channel, and Nuno Maduro, creator of Pest, Larastan, and Laravel Pint, and staff software engineer at Laravel.

This year’s lineup

PHP Foundation Keynote by Elizabeth Barron, Executive Director at the PHP Foundation.
My AI Writes Perfect* PHP by Ashley Hindle, Founder of Fuel and creator of Laravel Boost.
WordPress Is Dead, Long Live WordPress! by Jonathan Bossenger, Developer Advocate at Automattic.
Packagist Internals by Nils Adermann, Co-Founder at Packagist.
Running a Large Open-Source Project Like Symfony by Fabien Potencier, Founder and Project Lead at Symfony.
PHP RFCs by Larry Garfield, Functional Programming Enthusiast.
How AI Is Changing the Programmer World by Jeffrey Way, Founder at Laracasts.

For more information about the speakers and their talks, see the PHPverse 2026 page.

PHPverse 2025 recap

PHPverse took off last year as a celebration of PHP’s 30th anniversary, with over 15,000 viewers worldwide tuning in to the livestream. The event outreach and feedback showed how big and vibrant the PHP community is and why we should keep gathering every year to connect and learn from the people behind the major frameworks and tools.

You can catch up with recordings of last year’s talks:

I gotta say #PHPverse was awesome today! Well done to everyone who spoke for building so many awesome things! pic.twitter.com/lJttpMlxvG
— Liam Hammett (@LiamHammett) June 17, 2025

#PHPverse 2025 was such a valuable experience! We got practical advice from dope developers like @naderman (who happened to be co-host), also @jeffrey_way and @PovilasKorop.

My favourite session was: Laravel Q&A With @taylorotwell.

I feel super inspired to level up 💪#PHP30 pic.twitter.com/IT1vAksITr
— Timothy Samuel (@tsshekwogaza) June 17, 2025

Stay tuned

JetBrains PHPverse 2026 is free, online, and open to everyone. Register now, and we’ll send you a reminder email before the event. You can tune in for the whole day or drop in for the talks that interest you most.

Can’t make it on June 9? Register anyway, and you’ll receive the link with the talk recordings via email after the event.

In the meantime, join the event’s Discord server to receive the latest updates or drop your questions for the speakers – the event hosts will make sure to ask them during the Q&A sessions.

PHPverse grows as its community reach grows. Spread the word among your colleagues, use the #PHPverse hashtag in your social media posts, and help us bring more people into the conversation about the present and future of PHP.

See you at PHPverse!

PHP DateTimeImmutable::createFromFormat Reset Character - Blog entries :: mwop.net

2026-04-16T15:30:00.000Z

I was recently building something that was taking date input from an HTML form field, and casting it to a PHP DateTimeImmutable. I was then comparing that to another date, and got thrown off during testing when I compared the resulting instance to new DateTimeImmutable('today'); the instances were not considered equal.

To recreate the conditions, you can try the following:

$date     = '2016-06-16';
$fromForm = DateTimeImmutable::createFromFormat('Y-m-d', $date);
$today    = new DateTimeImmutable('today');
echo $fromForm == $today ? 'Equal' : 'Not equal'; // outputs "Not equal"

What's happening? Well, if you were to echo the results of each of $fromForm->format('c') and $today->format('c'), the difference is clear: the $fromForm value includes the time when the instance was created, while $today has the time set to midnight.

So, how do you zero out the time when using createFromFormat()?

It turns out that one of the format characters you can use is the | operator. When you include this at the end of your format string, any fields not included in the format are zero'ed out:

$fromForm = DateTimeImmutable::createFromFormat('Y-m-d|');

Reference

DateTimeImmutable::createFromFormat() Parameters

PHP DateTimeImmutable::createFromFormat Reset Character was originally published 16 April 2026 on https://mwop.net by Matthew Weier O'Phinney.

SQL ENUM Modification - Blog entries :: mwop.net

2026-04-08T20:34:00.000Z

I'm doing a little DB work recently, and needing to choose how to represent certain data in the database. For a few fields, ENUM would be the correct choice, but there's a possibility I would need to expand the ENUM later to add values.

My question: is this safe?

The short answer, in my research, is "yes", but with caveats.

For Postgres, it's trivial; you can easily add values to ENUM types:

ALTER TYPE some_previously_defined_enum ADD VALUE 'new-value';

For MySQL, it's a bit more complex. ENUMs are defined within the table schema, and to change them, you use an ALTER TABLE statement:

ALTER TABLE some_table
MODIFY some_previously_defined_enum ENUM('value-1','value-2');

Essentially, you're replacing the definition. This is fine... so long as you don't change the order, or remove any previously defined value in the ENUM. In other words, append to the existing list if you want to safely change it.

SQL ENUM Modification was originally published 8 April 2026 on https://mwop.net by Matthew Weier O'Phinney.

CSS Grid Lanes - Blog entries :: mwop.net

2026-04-07T15:38:00.000Z

I've been using the experimental "display: masonry" CSS for my gallery and a few other areas of my website for over a year (with a fallback to standard grid columns). However, I noticed in the last few months that my browser was no longer honoring it, and finally researched what happened.

It turns out it's been renamed to "display: grid-lanes" in the CSS Grid Level 3 specification. Otherwise, everything else remains the same; continue using grid-template-columns and grid-template-rows as you did with the the masonry display.

Safari has it in preview already, while Firefox and Chrome-based browsers have it behind a flag. (On Chrome-based browsers, visit chrome://flags, and enable the "css-grid-lanes-layout" flag.)

CSS Grid Lanes was originally published 7 April 2026 on https://mwop.net by Matthew Weier O'Phinney.

PhpStorm 2026.1 is Now Out - PhpStorm : The IDE that empowers PHP developers | The JetBrains Blog

2026-03-26T13:58:03.000Z

Welcome to PhpStorm 2026.1! This release brings new PhpStorm MCP tools, new third-party agents inside your IDE, support for Git worktrees, and lots of other productivity-enhancing features for PHP and Laravel developers.

Download PhpStorm 2026.1

PhpStorm MCP tools

In PhpStorm 2025.2, we added an integrated MCP server for third-party coding agents like Claude Code, Windsurf, or Codex to access and use your IDE’s tools.

In 2026.1, we are extending the MCP server toolset with more PhpStorm features, including:

Inspections and quick-fixes that enable agents to leverage PhpStorm’s powerful static analysis engine.
IDE search capabilities, including PhpStorm’s structural search and semantic search for code patterns.
Access to IDE actions so that you can delegate setup and customization of your IDE to your coding agent.

Furthermore, the PhpStorm plugin for Claude Code provides Claude Code with context and instructions for using PhpStorm MCP server tools. To add the plugin’s skills and hooks to your project, go to PhpStorm’s Settings | Tools | PHP Claude Skills.

Note: PhpStorm’s MCP server is disabled by default. To enable the server and configure integration with your coding agent, go to Settings | Tools | MCP Server.

AI

Third-party agents in PhpStorm

PhpStorm is evolving as an open platform that allows you to bring the AI tools of your choice into your professional development workflows.

In addition to Junie, Claude Agent, and most recently Codex, PhpStorm now lets you work with more AI agents directly in the AI chat. You can choose from agents such as GitHub Copilot, Cursor, and many others supported through the Agent Client Protocol.

Next edit suggestions

Next edit suggestions are now available without consuming AI quota of your JetBrains AI Pro, Ultimate, and Enterprise subscriptions. These suggestions go beyond traditional code completion for PHP. Instead of updating only what’s at your cursor, they intelligently apply related changes across the entire file, helping you keep your code consistent and up to date with minimal effort.

This natural evolution of code completion delivers a seamless Tab Tab experience that keeps you in the flow.

Junie CLI is now in Beta

Junie CLI is JetBrains’ LLM-agnostic coding agent you can use directly from the terminal, inside any IDE, in CI/CD, and on GitHub or GitLab. Junie CLI comes with:

Bring Your Own Key (BYOK) pricing, allowing you to use your own keys from model providers without additional charges.
One-click migration from other agents such as Claude Code or Codex.
Flexible customization through guidelines, custom agents and agent skills, commands, MCP, and more.

Read the full announcement in our blog post.

Project indexing optimization

PhpStorm now automatically detects framework-specific directories that contain frequently changing generated, cached, or user-uploaded content and excludes such directories from project indexing.

The IDE skips excluded folders during search, parsing, and other operations. Reducing indexing overhead helps optimize the CPU usage and performance of your IDE.

If you want to re-enable indexing for any of the automatically excluded folders, you can do so in Settings | Directories by clicking Exclude and unselecting the checkboxes next to the directories you want to be indexed.

Generics support

The new release brings a number of improvements and bug fixes for PhpStorm’s type inference engine, including:

Improved type inference for callable generic types. Now the IDE can infer both the input parameter type from a callable(T) annotation and the callable template return type.
Improved display for nested parameterized template types. PhpStorm 2026.1 displays parameter type (Ctrl + Shift+P) and quick documentation (F1) info with multiple layers of wrapping, such as Wrapper<Wrapper<Wrapper<stdClass>>>.

More quality-of-life improvements

Debugging non-PHP files

You can now set breakpoints in non-PHP files as soon as the file name pattern is associated with the PHP file type in the IDE settings. Together with native path mapping between templates and compiled PHP files introduced in Xdebug 3.5, this feature allows you to debug source template files of any format, including niche extensions like .ezt.

Improved Go to test navigation

In PhpStorm 2026.1, we’ve improved Go to Test navigation for PHPUnit and Pest tests with the following enhancements:

Navigation between PHPUnit tests that use a #[UsesClass] or #[UsesMethod] attribute and the related class/method.
For Pest tests, you can now navigate from the Test Runner tab to the source test nested inside Pest describe blocks.

Convert to pipe operator quick-fix

PhpStorm now detects code elements where the PHP 8.5 pipe operator syntax can be used and suggests a quick-fix to convert such code into easier-to-read pipe operator chains.

Laravel

Framework support: support for Laravel 13 and new versions of Livewire and Filament. Support for the new @hasStack and @includeIsolated Blade directives.
New package support: Laravel Wayfinder, PHP Native, staudenmeir/laravel-cte and staudenmeir/laravel-adjacency-list packages.
Eloquent enhancements: advanced #[Scope] methods support, optimized and more accurate Find Usages for scope, attribute and relation methods.
UI and navigation: Blade view usages UI, better controller inlays, new Route Search UI, and routes to the Endpoints tool window.
Productivity tweaks: a new Add Application Database action. Run Artisan commands in the Terminal tool window or via PHP interpreter.
Laravel Idea MCP server shipped with the PhpStorm MCP server.

For the full list of updates, see Laravel Idea’s changelog.

Frontend

PhpStorm’s TypeScript support now uses the service-powered type engine (built on the TypeScript language service) by default, delivering more accurate type inference and lower CPU usage in large projects. The TypeScript support is further improved with better auto-import handling for path aliases and project references, as well as the integration of inlay hints from the TypeScript Go-based language server. JavaScript parsing now also correctly handles string-literal import / export specifiers.

Framework and styling support have been refined across the board:

The IDE now highlights React’s new use memo and use no memo directives.
The Vue integration uses the updated 3.1.8 version of @vue/typescript-plugin.
Astro settings accept JSON-based configuration for language server integration.
Modern CSS color() functions and additional color spaces are supported in swatches and previews.
Angular 21.x template syntax is supported.

Databases

The AI chat integration for Codex and Claude Agent now offers full, native support for your connected databases. With that, you can now query, analyze, and modify your database state using natural language right from the IDE.

The same functionality is available for external agents via an MCP server.

Data source settings can now be stored in your JetBrains Account via data source templates. Especially nifty for All Products Pack users or anyone who uses multiple instances of JetBrains IDEs, this upgrade allows you to access data source templates and settings in every JetBrains IDE with database functionality.

Productivity-enhancing features

Editor caret and selection updates

We’re continuing to modernize our IDEs, and in this update, we’ve refreshed something you interact with constantly – the editor. Smooth caret animation and updated selection behavior provide improved comfort, a cleaner look, and a more enjoyable coding experience.

Work on multiple branches at once with Git Worktrees

With the evolution of AI agents, running multiple tasks in parallel has become a major time-saver, and this is precisely where Git worktrees are extremely handy. To support cutting-edge workflows for AI-boosted software development, PhpStorm now provides first-class support for Git worktrees. Create a separate worktree for an urgent hotfix, hand off another one to an AI agent, and keep working in your main branch – all at the same time, without interruption.

Even if you don’t use agents, worktrees will save you time on branch switching, especially in big projects.

Native Wayland support

IntelliJ-based IDEs now run natively on Wayland by default. This transition provides Linux professionals with ultimate comfort through sharper HiDPI and better input handling, and it paves the way for future enhancements like Vulkan support.

While Wayland provides benefits and serves as a foundation for future improvements, we prioritize reliability: The IDE will automatically fall back to X11 in unsupported environments to keep your workflow uninterrupted. Learn more.

Terminal completion

Stop memorizing commands. Start discovering them. In-terminal completion helps you instantly explore available subcommands and parameters as you type. Whether you’re working with complex CLI tools like Git, Docker, or kubectl or using your own custom scripts, this feature intelligently suggests valid options in real time.

Code With Me sunset

As we continue to evolve our IDEs and focus on the areas that deliver the most value to developers, we’ve decided to sunset Code With Me, our collaborative coding and pair programming service. Demand for this type of functionality has declined in recent years, and we’re prioritizing more modern workflows tailored to professional software development.

As of version 2026.1, Code With Me will be unbundled from all JetBrains IDEs. Instead, it will be available on JetBrains Marketplace as a separate plugin. 2026.1 will be the last IDE version to officially support Code With Me, as we gradually sunset the service.

Read the full announcement and sunset timeline in our blog post.

Create an HTML version of an OpenAPI spec - Rob Allen

2026-03-17T11:00:00.000Z

I have a new project where we will be integrating with a third party API that is currently being written. Due to Conway's Law, we are being sent new versions of the OpenAPI spec as a set of JSON files via email.

I quite like seeing the HTML rendering of an OpenAPI spec when reading it and understanding it, so I knocked up a simple shell script that takes an OpenAPI spec file and outputs an HTML doc. This is a trivial task thanks to Scalar!

This is the script:

~/bin/create-openapi-spec-doc.sh:

#!/usr/bin/env bash

set -eo pipefail

if [[ $# -eq 0 ]]; then
  echo "Usage: $(basename "$0") <spec-file> [spec-file ...]"
  echo "Generates an HTML API reference document for each OpenAPI spec file provided."
  exit 1
fi

for spec_file in "$@"; do
  base="${spec_file%.*}"
  spec_name="$(basename "$base")"

  {
    cat <<EOF
<!doctype html>
<html>
  <head>
    <title>${spec_name} API</title>
    <meta charset="utf-8" />
    <meta
      name="viewport"
      content="width=device-width, initial-scale=1" />
  </head>

  <body>
    <div id="app"></div>
    <script
      id="api-reference"
      type="application/yaml">


EOF
    cat "$spec_file"
    cat <<'EOF'
    </script>

    <!-- Load the Script -->
    <script src="https://cdn.jsdelivr.net/npm/@scalar/api-reference"></script>
  </body>
</html>

EOF
  } > "$base".html

  echo "Generated: $base.html"
done

$ create-openapi-spec-doc.sh *.json Generated: provided_svc.html Generated: required_svc.html

and now I have nicely formatted HTML files!

PHPStan custom rules - Rob Allen

2026-03-03T11:00:00.000Z

Recently I discovered that this code passed our PHPStan level 10 checks:

use http\Exception\InvalidArgumentException;


// ...

throw new InvalidArgumentException;

I was surprised as http\Exception\InvalidArgumentException is not a class in our system. While cooling, I discovered that there's an http PHP extension and it appears that PHPStan has a stub for this which means that it accepts it as existing even if it doesn't.

What we think happened is that I wrote throw new InvalidArgumentException; and selected the wrong class from the dropdown in PHPStorm as I wanted to import the base InvalidArgumentExtension

I want PHPStan to fail in this case, so I wrote a PHPStan extension that calls class_exists() to ensure that the class really is available:

<?php

declare(strict_types=1);

namespace Laminar\PHPStan\Rules;

use PhpParser\Node;
use PhpParser\Node\Stmt\Use_;
use PHPStan\Analyser\Scope;
use PHPStan\Reflection\ReflectionProvider;
use PHPStan\Rules\Rule;
use PHPStan\Rules\RuleError;
use PHPStan\Rules\RuleErrorBuilder;
use PHPStan\ShouldNotHappenException;

/**
 * Flags imported classes that PHPStan knows about via bundled extension stubs
 * but cannot be loaded in the current runtime environment.
 *
 * This rule checks using the xxx_exists() functions, so is only useful if run within
 * a context that matches deployment.
 *
 * @implements Rule<Use_>
 */
class ImportedClassExistsRule implements Rule
{
    public function __construct(private readonly ReflectionProvider $reflectionProvider)
    {
    }

    public function getNodeType(): string
    {
        return Use_::class;
    }

    /**
     * @return list<RuleError>
     * @throws ShouldNotHappenException
     */
    public function processNode(Node $node, Scope $scope): array
    {
        if ($node->type !== Use_::TYPE_NORMAL) {
            return [];
        }

        $errors = [];

        foreach ($node->uses as $use) {
            $className = $use->name->toString();

            if (! $this->reflectionProvider->hasClass($className)) {
                continue;
            }

            if (
                class_exists($className)
                || interface_exists($className)
                || trait_exists($className)
                || enum_exists($className)
            ) {
                continue;
            }

            $errors[] = RuleErrorBuilder::message(
                sprintf(
                    'Imported class %s does not exist at runtime. The required PHP extension may not be installed.',
                    $className,
                ),
            )->identifier('akrabat.importedClassExists')
            ->line($use->getLine())
            ->build();
        }

        return $errors;
    }
}

The only important thing you need to know about writing a custom PHPStan rule is that processNode() returns an array of errors and if that is empty, then the rule succeeded.

This one isn't particularly complicated, but it solves the problem!

As an aside, to prevent PhpStorm from providing autocomplete for extensions that don't exist in your application, go to Settings→PHP and select the PHP Runtime tab. You can then select the extensions you use and deselect those that you don't. There's even a "Sync Extensions with Interpreter" button which can be handy if you build your dev container from your prod one.

Feelings - Rob Allen

2026-02-27T22:16:58.000Z

Today has been a struggle entirely due to my own internal negative thoughts and feelings about impacting events that are outside my control.

Navigating this to come out stronger rather than letting it consume my self-belief and confidence isn’t easy, especially at the time. I’m not worse at my job and my abilities haven’t diminished, but sometimes it’s hard to remember this.

I need to give myself space to remember who I am and internalise that my emotions are valid, but not the whole truth. Introspection and understanding of the whole is important.

Onwards and upwards.

Headless boot for Beelink EQ14 - Blog entries :: mwop.net

2026-02-24T16:09:08.000Z

A few months back, I purchased a Beelink EQ14 mini server for my homelab. One thing that has frustrated me has been that rebooting or even powering on... has required I have either my keyboard or my monitor plugged in (I haven't been able to determine exactly which one yet). This has made me reluctant to reboot, as I then have to switch my keyboard from my workstation over to the server, and plug the HDMI from one of my monitors into it. I hate it.

In browsing a number of forums, I saw one recommendation to switch the BIOS to use FastBoot.

Can confirm, works!

Headless boot for Beelink EQ14 was originally published 24 February 2026 on https://mwop.net by Matthew Weier O'Phinney.

Globbing files to pass to CLI command options - Blog entries :: mwop.net

2026-02-18T19:56:00.000Z

I've been using Helm recently as part of a new product offering, and as a way to deploy my various websites. Helm allows providing values to the templates in a Helm chart via one or more values files, which are provided via the option -f. It's often useful to break these into several files, so you can do things like cover common values, and then environment- or namespace-specific values.

However, the -f option only accepts a single value, and doesn't recognize globs.

The printf solution

The solution is to pass the glob to printf, with the format '-f %s '. This will print out an option per file.

When in a terminal, this can be done using printf within a subshell. Now how you do that depends on the shell, because the -f in our format string can be interpreted as an option/flag to printf itself depending on the shell.

For bash, we can do this:

helm upgrade -n qa . $(printf -- '-f % ' *.values.yaml)

This is because printf in bash will emit an error for any unknown option/flag it encounters; the -- tells the command when the end of all options/flags have been reached, so that it treats the remainder as arguments.

For fish, we don't need the --, as the printf implementation in fish doesn't accept arguments anyways:

helm upgrade -n qa . $(printf '-f % ' *.values.yaml)

Makefile

Of course, subshells in a Makefile require a little change as well. In a Makefile, I write the above as:

helm upgrade -n qa . $(shell printf -- '-f %' *.values.yaml)

(And since I also declare SHELL=/bin/bash at the top of my Makefile, I have to use the -- trick here.)

Globbing files to pass to CLI command options was originally published 18 February 2026 on https://mwop.net by Matthew Weier O'Phinney.

Removing a filename containing a null byte or binary character on Linux - Blog entries :: mwop.net

2026-02-06T17:01:27.000Z

Somehow, I got a file in my tree that started with a null byte. I only discovered it because git status was noting it wasn't added to my branch, and wanted to know if I wanted to add it.

No, no, I did not. I wanted to delete it.

But, of course, you cannot reference such a file by name, so I had to learn a few tricks.

First off, you can list names with binary bytes using:

/bin/ls -lb

But even better, you can get the inode if you use:

/bin/ls -li

When you do, the inode is in the first column of the list for each file.

Once you know that, you can delete the file, using find:

find . -maxdepth 1 -inum <inode_id> -exec rm -i -- {} +

Removing a filename containing a null byte or binary character on Linux was originally published 6 February 2026 on https://mwop.net by Matthew Weier O'Phinney.

Dad - Rob Allen

2026-01-22T15:00:00.000Z

I don't often post personal things here, however last weekend my dad died peacefully in his sleep and it feels important to acknowledge this.

I have no words.

2025 in pictures - Rob Allen

2025-12-31T17:52:04.000Z

As we reach the end of 2025, I take this opportunity to look back over the photos that I have taken and thing about the year. This year I published 1,064 photos to Flickr with, of course, at least one photo every day as part of my Project 365.

The lovely thing is that my photos remind me what happened during my year and I remember many good times through them as I've seen friends and family over the months. I've done for many years now and you can see them all in my Year in pictures category.

January

I started the year visiting the Severn Valley Railway and took some photos of steam trains. I also visited PHP Stoke which was fun.

February

I attended three community events in February, starting with FOSDEM at the very start, PHP UK mid-way through, and then Fusion towards the end. I really like catching up with the community and learning from them in the hallway track! I also photographed planes with Stuart!

March

I had a quick trip to Spain this month which was very cold and wet and then spoke at Drupal Mountain Camp; my first time attending this conference and I loved the community vibe here. I was also enjoyed my visit to the KVWR with Kevin.

April

In April, I went down to London to take care of my dad while my mum visited her sister in America. I fitted in a trip to the SVR Spring Gala, and also spoke at PHP Berkshire, sharing the bill with Dave Liddament

May

We celebrated lots of birthdays in May and visited Dudley Canal & Caverns. I spoke at phpday in Verona and later the PHP Oxford user group. The community at both events are fantastic and I enjoyed all the great conversations. My wife and I also enjoyed a visit to Charlecote. Most importantly, Crystal Palace won the FA cup this month for the first time in their history!

June

The Nintendo Switch 2 was released this month and it's a great sequel to the original Switch. We spent most of the month on holiday in Spain, where I ate lots of ice cream.

July

July was all about family and friends. My aunt and cousins from America visited, so we moved our family meet-up to July. We also had our regular lunch with friends in Crewe as that's half-way between us. We also celebrated our youngest's graduation of a first class degree in mathematics.

August

There was a big railway event in August celebrating 200 years of the modern railways. I visited mum & dad and I took dad out for breakfast at the local café which turned out to be the last time that dad and I will do that. We also visited our friend in Estonia.

September

The big news in September is that my dad's wellbeing deteriorated far enough that mum was no longer able to care for him. He was taken to hospital and is now living in a care home. I'm pleased that the transition seems to have gone smoothly for both of them. Later that month, I attended apidays London and then took a few days to take photos of trains in Yorkshire, while catching up with good friends in the evenings. The Moors really are a lovely place to spend time.

October

In October, my aunt from America visited again which was lovely as she stayed with my mum, arriving a few days after dad had moved into a care home. I also spoke at Nordic APIs Platform Summit in Stockholm. I was surprised to be on the main track and the conference as a whole was excellent. Finally, we celebrated another graduation as my wife graduated with a first class degree in Computing.

November

A quiet month, where I spoke at SymfonyCon which celebrated the 20th anniversary of the framework.

December

I finished the year attending apidays Paris, my first visit to this very large conference, where I met some amazing people and learned things. We had a lovely Christmas at home where lots of cake and mince pies were consumed. Then, right at the end of the month, I visited the SVR for the final time this year to take photos of heritage diesel locomotives. I also bought a new camera for next year!

Looking back over 2025, it was a bittersweet year with some excellent times with family, friends and community folks, but it was tinged with my dad's transition to a care home. As always, I also very much enjoyed my railway photography and trips with Stuart.

Who knows what 2026 will bring, but I will continue to take photos throughout!

Built-in Laravel Support: A New Era for PhpStorm Developers - PhpStorm : The IDE that empowers PHP developers | The JetBrains Blog

2025-12-10T17:02:10.000Z

For years, PhpStorm has been the go-to IDE for PHP developers – powerful and deeply integrated with the language. But there was one thing many kept asking for: Laravel support out of the box.

It should come with built-in
— Amdadul Haq (@amdad121) July 30, 2025

Starting with PhpStorm 2025.3, Laravel support is now built in. From the moment you open your project, everything just works – no plugins, no configuration, no extra steps.

Discover the story behind this update from PhpStorm Team Lead Roman Pronskiy, PhpStorm Software Developer Maria Filippova, JetBrains Product Lead Artemy Pestretsov, Laravel Idea plugin creator Adel Faizrakhmanov, Laravel creator Taylor Otwell, and JetBrains Developer Advocate for PHP Brent Roose:

Start your Laravel journey

FAQ

I use IntelliJ IDEA. How is Laravel support provided there?

In IntelliJ IDEA, you can install the Laravel Idea plugin as usual from the main menu: File | Settings | Plugins | Marketplace → “Laravel Idea”.

Will the standalone Laravel Idea plugin continue to be maintained?

Yes. Adel and the PhpStorm team will continue collaborating to ensure the plugin – and PhpStorm’s integrated support – remain the top-tier Laravel development experience in the industry.

Is Laravel support available if I’m using PhpStorm for free?

Yes. The built-in Laravel support is available to all PhpStorm users, including those using:

The 30-day free trial.
Early access builds.
Free licenses, such as licenses for students, teachers, open-source projects, or startups.

If you can run PhpStorm, you can use Laravel support – no limitations.

I use PhpStorm. Can I now uninstall the Laravel Idea plugin?

In PhpStorm, the Laravel Idea plugin now comes pre-installed and enabled, so you no longer have to download or manage it manually. However, you should keep the plugin enabled; disabling or removing it will turn off all Laravel-specific features.