-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
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
vue-cli 3 & absolute path bug & baseUrl bug #2595
Comments
Hello, your issue has been closed because it does not conform to our issue requirements. In order to ensure every issue provides the necessary information for us to investigate, we require the use of the Issue Helper when creating new issues. Thank you! 你好,你的 issue 不符合我们所要求的格式,因此已被自动关闭。为了确保每个 issue 都提供必需的相关信息,请务必使用我们的 Issue 向导 来创建新 issue,谢谢! |
Did you read the docs? |
@Akryum a better help for him (and everyone else) would be a deep link to explain. |
@Akryum THX!
module.exports = {
lintOnSave: false,
configureWebpack: {
resolve: {
extensions: [
".js",
".json",
".vue"
],
},
},
baseUrl: "./xxx/" ,
// baseUrl: process.env.NODE_ENV === "production" ? "./" : "./",
};
|
ok & but very confused
module.exports = {
lintOnSave: false,
configureWebpack: {
resolve: {
extensions: [
".js",
".json",
".vue"
],
},
},
baseUrl: "././" ,
// baseUrl: "./" ,
// baseUrl: process.env.NODE_ENV === "production" ? "./" : "./",
outputDir: "build",
filenameHashing: false,
crossorigin: "anonymous",
integrity: true,
};
|
|
请问现在解决了 我同遇见 |
不知道为什么,不过确实有用。。 |
谢谢你 我也是这个问题 你这个方法的确可以解决 |
ok & but very confuse |
absolute path bug
环境信息
问题描述
错误信息
wanted
The text was updated successfully, but these errors were encountered: