Do you use yarn workspaces or something similar?
-
-
Replying to @WebStormIDE
I think it's similar yeah, but didn't read before. We just have several processes for all the stuff. Server containers really decoupled. We can have N number of APIs and, web server and frontend. The selected area is the one I need WS to acknowledge.pic.twitter.com/3yzDDfJKCR
1 reply 0 retweets 0 likes -
Replying to @ant_laguna @WebStormIDE
I'm OK telling WS to ignore any folder but it seems that stuff that's not on a root package.json is not acknowledged.
2 replies 0 retweets 0 likes -
Replying to @ant_laguna
Can you please also check the list of libraries in Preferences | Languages & Frameworks | JavaScript | Libraries - all the node_modules libraries should checked.
1 reply 0 retweets 0 likes -
Replying to @WebStormIDE
It wasn't fully checked but semi-checked (whatever that state means). I've checked it fully to see if it made any difference and no dice. I can see "library root" as your state but see this:pic.twitter.com/GZRmv1qcDG
1 reply 0 retweets 0 likes -
Replying to @ant_laguna
What is the path to this script.js file? Is it in the clientkit folder or elsewhere?
1 reply 0 retweets 0 likes -
-
Replying to @ant_laguna
That might be the reason - this inspection follows the standard patterns and checks the package.json files in the parent folders. Will see if where's a workaround. But code completion should actually work just fine in this case. Does it?
1 reply 0 retweets 0 likes -
Replying to @WebStormIDE @ant_laguna
You can disable the inspection if you press Alt-Enter on it, then arrow right - Disable inspection.
1 reply 0 retweets 0 likes -
Replying to @WebStormIDE @ant_laguna
Do you use webpack in your project? Do you have these resolve rules described in resolve.module in the webpack config? If yes, WebStorm can understand that config - specify the path to it in Preferences | Languages & Frameworks | JavaScript | Webpack.
2 replies 0 retweets 0 likes
The missing module dependency inspection will then correctly check the modules in different folders.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.