@WebStormIDE how can I make WS not consider internal variables from packages as global variables? Common variable names are always a pain to get auto-import working. Thanks!pic.twitter.com/wpTIIXKCiA
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Unfortunately, it's not always possible to be sure which variable is internal and which is not. WebStorm will first try to navigate to and autocomplete symbols that are more strictly resolved (e.g. imported in the current file or defined in d.ts)...
But if it can't be 100% sure, it will show more symbols - because of the dynamic nature of JavaScript it could still be a valid match.
A possible workaround could be disabling the node_modules library in Preferences | Languages and Frameworks | JavaScript | Libraries and using only TypeScript type definition files for all your dependencies: https://www.jetbrains.com/help/webstorm/configuring-javascript-libraries.html#ws_jsconfigure_libraries_ts_definition_files …
Got similar question. How to make suggestions sorted (first project variable then node_modules/ lib. I always see first node modules files when opening new file. Eg. looking for package (.json) shows project file at the very bottom 
Hi, do you mean when using the Go to file action?
IMHO, no variable should be considered global unless explicitly made global. Also, it just behaves this way for certain names. I'll come with a repo with many examples of misbehavior later this week. Hopefully it'll make it clearer for you to fix it.
How exactly it could be marked as global? In your example, is there a `colors` variable defined somewhere in your project that should be in the list of definitions instead?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.