We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
在使用路径别名的情况下,"@/": ["src/"] 和 "@src": "src" 两种写法都可以实现相同的效果,即将路径别名映射到对应的源代码目录。
"@/": ["src/"]
"@src": "src"
然而,根据个人偏好和项目的具体需求,可以选择更适合的写法。以下是对两种写法的比较:
优点:
因此,选择哪种写法取决于具体的项目需求和个人喜好。如果项目结构较为复杂,需要针对不同的目录进行路径别名配置,或者希望使用通配符匹配多个文件或目录,那么使用"@/": ["src/"] 的写法可能更适合。如果项目结构相对简单,路径别名的映射关系较为直接,且不需要通配符功能,那么使用"@src": "src" 的写法会更简洁和易于管理。
The text was updated successfully, but these errors were encountered:
No branches or pull requests
在使用路径别名的情况下,
"@/": ["src/"]
和"@src": "src"
两种写法都可以实现相同的效果,即将路径别名映射到对应的源代码目录。然而,根据个人偏好和项目的具体需求,可以选择更适合的写法。以下是对两种写法的比较:
优点:
缺点:
优点:
缺点:
因此,选择哪种写法取决于具体的项目需求和个人喜好。如果项目结构较为复杂,需要针对不同的目录进行路径别名配置,或者希望使用通配符匹配多个文件或目录,那么使用"@/": ["src/"] 的写法可能更适合。如果项目结构相对简单,路径别名的映射关系较为直接,且不需要通配符功能,那么使用"@src": "src" 的写法会更简洁和易于管理。
The text was updated successfully, but these errors were encountered: