NoBody Posted April 15, 2020 Report Posted April 15, 2020 Hi, I was trying to do some code with this npm package and everything was fine but webstorm still warns me that client.on() is undefined but it's working just fine but it is really annoying to have it there. Is there any way to fix that, I'm kinda new into this stuff so I don't know if I should change something in steam-user package to satisfy webstorm or just leave it be... Quote
Dr. McKay Posted April 15, 2020 Report Posted April 15, 2020 Update to 4.13.3 and that warning should go away. Quote
Xertz Posted April 16, 2020 Report Posted April 16, 2020 5 hours ago, Dr. McKay said: Update to 4.13.3 and that warning should go away. Have made sure I'm on `4.13.3` and I'm also still getting the error in Webstorm NoBody 1 Quote
NoBody Posted April 16, 2020 Author Report Posted April 16, 2020 Thanks for taking fast actions but I'm also getting unresolved method warning even after update. :\ Quote
Dr. McKay Posted April 16, 2020 Report Posted April 16, 2020 It seems that WebStorm gets confused by @extends in modules for some reason. v4.14.0 should properly make WebStorm understand what's going on. Quote
NoBody Posted April 16, 2020 Author Report Posted April 16, 2020 I try update and reinstall whole package and even try rebuild cache but I still get same message as before, webstorm is really confused, or is there maybe somethink what I'm doing wrong? maybe reinstall all packeges? Quote
Dr. McKay Posted April 16, 2020 Report Posted April 16, 2020 You could try that. It works for me. Quote
Xertz Posted April 17, 2020 Report Posted April 17, 2020 Can confirm 4.14.0 solves this - thanks so much @Dr. McKay! Quote
NoBody Posted April 17, 2020 Author Report Posted April 17, 2020 Thank you @Dr. McKay, I just need to make new project but it's working now... now it's look perfect Quote
NoBody Posted April 18, 2020 Author Report Posted April 18, 2020 So, after I made new project just with steam-user package it works, but after I installed all other modules that I needed it won't worked again so I dug deep into problem and I find out that problem was caused by @types/node module, @Dr. McKay any idea why? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.