unresolved function or method Object.values() Follow

Works for me:

please try ctrl+clicking on Object - what definition are you taken to?

Hi Elena,

This is what I get:

Please Ctrl+click on Object, not on values

Sorry did not read properly..  #classic

And the Object interface is coming from here (not sure if is helpful)

hmmm... what language is it? JavaScript or Typescript?

Typescript 

"typescript": "~2.3.3"

Make sure to add

"lib": ["es2017"]

to your tsconfig.json and enable TypeScript service in Settings | Languages & Frameworks | TypeScript

I had that already.. since i'm using angular-cli I have 2 tsconfig.json files more. could this cause the issue?

I just tried in the project with a .JS file and it works, only not for Typescript :(

>since i'm using angular-cli I have 2 tsconfig.json files more. could this cause the issue?

No; in your project, you actually have a single configuration file - only tsconfig.json files are respected, tsserver doesn't work with files like tsconfig.app.json

Works for me using same settings:

can you check if the service was started successfully? What is logged in TypeScript tool window?

That's maybe it Elena, 

The service has not started, even though as you saw above is turned on. how can I automatically start it? The icon "restart typescript service" does not do anything, and I don't want webstorm to compile my typescript files since I already have webpack doing so.

Try changing Typescript version to Bundled in Preferences | Languages & Frameworks | TypeScript, restart the service and make any change to your file (i.e. add a whitespace) - what is the result?

I did change it to bundled (2.4.1) and add a console.log(''). how can I restart the typescript service?

maybe i need some extra plugin?

>how can I restart the typescript service?

using "restart typescript service" button.

If it doesn't help, this may indicate issues with your project (missing/excldued tsconfig.json, for example - service only works when it's available)

Thank you, Elena.

For my case, changing to

"lib": [
  "es2017",
  "dom"
]

in tsconfig.json did the trick.

Cheers.

In my case was only fixed by upgrading WebStorm to WebStorm-EAP..