[Help wanted] Can't resolve 'postcss-loader' #41
Answered
by
meteorlxy
Mister-Hope
asked this question in
Q&A
-
Using import type { UserConfig } from "@vuepress/cli";
import type { DefaultThemeOptions } from "@vuepress/theme-default";
const config: UserConfig<DefaultThemeOptions> = {
base: process.env.VuePress_BASE || "/",
title: "Add this",
description: "VuePress 的 Add this 插件",
head: [
["link", { rel: "icon", href: "/favicon.ico" }],
["meta", { name: "author", content: "Mr.Hope" }],
[
"meta",
{
name: "viewport",
content:
"width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, viewport-fit=cover",
},
],
],
dest: "./dist",
locales: {
"/": {
lang: "zh-CN",
},
},
themeConfig: {
logo: "/logo.svg",
locales: {
"/": {
nav: [{ text: "主页", link: "/" }],
lang: "zh-CN",
selectText: "选择语言",
lastUpdatedText: "上次编辑于",
label: "简体中文",
},
},
},
};
export default config; |
Beta Was this translation helpful? Give feedback.
Answered by
meteorlxy
Jan 31, 2021
Replies: 4 comments 5 replies
-
|
Addtional info: I found postcss-loader in yarn.lock: More addtional info:
I am very confused yarn thinks But if I remove it and run yarn install again, it's gone:
Any ideas? @meteorlxy |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I have noticed that. It is caused by the postcss version conflict. We have upgrade to postcss 8, but vue core has not yet. |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
So is there a bypass now? I can not even serve or build now.'👀 |
Beta Was this translation helpful? Give feedback.
-
Didn't that solve it? 🤔 I thought it should work |
Beta Was this translation helpful? Give feedback.
-
|
I tried, but I remember there are still some errors, I will check again now. |
Beta Was this translation helpful? Give feedback.
-
After adding it ( version 4.2.0) |
Beta Was this translation helpful? Give feedback.
Answer selected by
Mister-Hope
-
|
I put vuepress to my repo and got same errors, adding these packages solve it: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I had this problem after upgrading to beta.27, but I solved it after deleting the |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
This did not fix the issue for me. Also on beta.27. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have noticed that. It is caused by the postcss version conflict. We have upgrade to postcss 8, but vue core has not yet.
vuejs/core#2710