Project Load Problem after Update from Php Storm 2017.3 to 2018.2

My Project is not Loading after Update my PHPStorm on Linux from 2017.3 to 2018.2.

I have a Project thats load only if i delete the Package.json. the Package.json is identical with an other Package.json on other Project thats load fine.

I have tried to delete the .idea Folder and the complete .PhpStorm2018.2 config folder with no result, if the Package.json exist the Project not Loads.

i change Back to 2017.3 and it works fine.

I have no idea what can i do to load the Project on 2018.2


If you copy this package.json into a new project and try to open the project - would it be OK?
If it's still bad, we'll need to take a look at this file. Could you please share it?


if i copy the package.json to an new or old other project its works fine.

the package.json:

    "private": true,
    "scripts": {
        "dev": "npm run development",
        "development": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
        "watch": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
        "watch-poll": "npm run watch -- --watch-poll",
        "hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js",
        "prod": "npm run production",
        "production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"
    "devDependencies": {
        "axios": "^0.17",
        "bootstrap": "^4.0.0",
        "popper.js": "^1.12",
        "cross-env": "^5.1",
        "jquery": "^3.2",
        "laravel-mix": "^2.0",
        "lodash": "^4.17.4",
        "vue": "^2.5.7"



Might be some custom plugin. Please try to disable them all and check the behavior.

Also, is anything being written into IDE logs when you reproduce this error?


i don't know why but the Problem is today gone away. Look like some system Update  this week has resolved it. Thx for Helping


Please sign in to leave a comment.