"Cannot resolve symbol" issue in Vue.js app

Hi,
I'm using PHPStorm 2024.2 on Windows 11, working in WSL and using Docker containers. I installed fresh Vue.js app from the Node.js container. In all import statements from 'vue' the IDE says "Cannot resolve symbol ...". I marked the "frontend" folder as Resource root directory. Am I doing something wrong?
Thanks for help in advance.

Update 1: Just updated to PHPStorm 2024.2.1, did not solve the issue.

0
6 comments
Hello,
Unfortunately, it is difficult to determine the cause of the issue based on this information. As far as I understand it is not the only error in the editor. Please share a screenshot of the Problems tool window. Also, could you please attach the logs from the language service? 
To collect service logs please go to Help | Diagnostic Tools | Debug Log Settings… and add #com.intellij.platform.lsp to the Custom Debug Configuration window.
Then restart the IDE, reproduce the issue, and send us all the IDE logs collected via Help | Collect Logs and Diagnostic Data….
Also, please share a screenshot of the Settings | Languages & Frameworks | TypeScript and Settings | Languages & Frameworks | Node.js settings. 

0

Hello Natalia,
Thanks for the reply! Below are the screenshots from the “Problems tool” and “Settings > Languages & Frameworks > Node.js” windows. Also, I created a log archive using Help > Collect Logs and Diagnostic Data. It is a 7 Mb zip file. How can I send it to you? Should I create and submit a request using "Contact support" button and attach the file there?

0
Hello, 
You can upload the logs here: https://uploads.jetbrains.com. Please let me know the upload ID after that.
0

Thank you.

Upload id: 2024_09_27_759pdspDdUrPGxjhgSz6kb (file: phpstorm-logs-20240927-1304375069472899847929445.zip)

0

Hello Natalia,

I'm sorry, I guess I found the cause. Looks like the dependencies were installed to the "node_modules" folder not correctly. I think, last time I interrupted installation as I can remember. Now, I created totally new project, waited for full npm installation, and now it's all fine, there is no that warning anymore.
Please, sorry for wasting your time. This post now can be closed.

0
No worries. It is great news that the issue is resolved. Thank you for letting me know.
0

Please sign in to leave a comment.