Vue-router.mjs conflict occurred after Vue3 project introduced public modules: How to solve the problem of useRouter() returning undefined?

Vue3 project: Solutions for the introduction of public modules that lead to vue-router conflict and useRouter() return undefined

This article analyzes and solves the problem of useRouter() returning undefined in Vue3 project after introducing public modules, and debugging shows that there is a conflict between two vue-router.mjs files.

Problem description: The system management module (system) depends on the common module (common), which contains routing configuration (route.js) and Vue Router references. After publishing the common module to the intranet Nexus, after the system module is introduced into the common module, useRouter() returns undefined . The debugging shows that the project has two vue-router.mjs files. However, using yarn link @ht/common to introduce common module, the problem disappears.

The root cause of the problem: both the common module and the system module rely on vue-router. Since the common module is published to the intranet Nexus in the form of an npm package, the system module is installed through npm, resulting in two vue-router versions installed in the project, causing conflicts. yarn link creates symbolic links, avoiding duplicate installations.

Solution: Make sure the project uses only one version of vue-router. The following methods are available:

1. Version consistency: Check package.json of common and system modules to ensure that the vue-router version is consistent. The version is inconsistent, so you need to adjust the vue-router version of one of the modules.

2. Dependency enhancement: Remove vue-router from dependencies of the common module and declare it directly in dependencies of the system module. The system module will install vue-router directly from the project root directory to avoid version conflicts. The routing configuration of the common module needs to be adjusted accordingly so that it no longer directly depends on vue-router.

3. Module structure optimization: Reevaluate common module design. If the common module only provides common components and tool functions, the routing configuration should not be included. The routing configuration should be placed in the system module or a higher-level routing configuration module.

Through the above method, the vue-router version conflict can be effectively avoided and the problem of useRouter() returning undefined . The core is to ensure that only one version of vue-router in the project is loaded and used correctly.

The above is the detailed content of Vue-router.mjs conflict occurred after Vue3 project introduced public modules: How to solve the problem of useRouter() returning undefined?. For more information, please follow other related articles on the PHP Chinese website!