# Xdebug + PhpStorm add-on doesn't work **URL:** \ **Category:** Xdebug + PhpStorm\ **Tags:** phpstorm, xdebug, add-on\ **Created:** [July 8, 2021, 2:59pm UTC](https://community.localwp.com/t/xdebug-phpstorm-add-on-doesnt-work/26404 "2021-07-08T14:59:31Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![ben.turner](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/ben.turner/32/5366_2.png) [@ben.turner](https://community.localwp.com/u/ben.turner)\ **Post date:** [July 9, 2021, 9:43pm UTC](https://community.localwp.com/t/xdebug-phpstorm-add-on-doesnt-work/26404/2 "2021-07-09T21:43:31Z")
Thanks for posting all of this and making use of Local and Xdebug! That script is what Local uses to help define the `WP_ENVIRONMENT_TYPE` variable. There’s more discussion about this in the following topic along with some adjustments that can be made to prevent this PHPStorm from breaking on this file: > **[Local-bootstrap.php is triggering a breakpoint when XDebug is enabled](https://community.localwp.com/t/local-bootstrap-php-is-triggering-a-breakpoint-when-xdebug-is-enabled/22229)** > > I just wanted to post a solution to this issue in case anyone else is using PHPStorm and experiences it. What’s happening is that after the latest update to Local (5.7.5+4909) there is now a file that Local is using that is outside the WP... If it interests you, you can also upvote this feature request to remove this file: > **[Don't define WP\_ENVIRONMENT\_TYPE](https://community.localwp.com/t/dont-define-wp-environment-type/24587)** > > Issue Summary If other plugins define the constant WP\_ENVIRONMENT\_TYPE then a PHP warning is displayed as the constant is already defined. I develop plugins that allow the user to change this setting and having this define in the... --- _[View the full topic](https://community.localwp.com/t/xdebug-phpstorm-add-on-doesnt-work/26404)._