Is there a conflict between the node_modules folder generated during project creation and some third-party libraries

[Sky-Runner-Z]

When I create a Vue project like the one shown in the picture, a 'node_modules' folder is automatically generated in the project folder to manage dependency libraries. However, when I use 'npm install vue router -- save' or 'npm install element plus -- save' to download third-party libraries, I cannot use the contents of these libraries properly and the webpage always reports errors -- for example: Cannot read properties of null (reading 'ce') TypeError: Cannot read properties of null..
But when I deleted the original 'node_modules' folder and ran the 'npm install' command to regenerate the new 'node_modules' folder, it could run normally. Why is this happening? Is it because there is a dependency conflict in the original 'node_modules' modules?

[Hetari]

Well, I don't know if there's a specific conflict or not, but I highly recommend creating your Vue project using Vite instead of the traditional Vue CLI.

Why Use Vite?

1. Faster Development
2. Better Dependency Management
3. Hot Module Replacement (HMR)
   and more...

How to Set Up a Vue Project with Vite

1. Create a New Vue Project:

npm create vite@latest

chose vue, then js or ts. and go to the project folder to install all dependencies. That's it!

Using Vite might avoid issues related to dependency conflicts or installation problems. Give it a try!

https://vite.dev/

[Sky-Runner-Z]

Thank you very much for your suggestion, it is really helpful!!