blocks|key|2093597|text|我发现有一个对象没有生成页面所需的属性。一旦我移除了它，一切都变好了|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2093598|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I discovered that there was an object without a property that was needed to generate the page. Once I removed it, all was well

blocks|key|2088891|text|已通过输出以下日志解决此问题。所有页面都已被记录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2088892|export+async+function+getStaticProps({+params:+{slug}+})+{
++//+↓add+
++console.log(`Building+slug:+${slug}`)
}|code-block|syntax|javascript|2088893|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

The problem was resolved by outputting the following log.
All pages have been logged.
<pre><code>export async function getStaticProps({ params: {slug} }) {
 // ↓add 
 console.log(`Building slug: ${slug}`)
}
</code></pre>

blocks|key|2944949|text|我也得到了这个错误。我发现我正在使用一个没有道具的组件。移除它或传递道具就可以解决这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2944950|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I got this error too. I found out that I was using a component without props.
Removing it or passing props will fix the issue

blocks|key|2944996|text|像这样添加回退对我来说很有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2944997|{fallback:+false}|offset|length|style|CODE|2944998|entityMap^0|0|0|H|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Adding fallback like this worked for me:
<code>{fallback: false}</code>

blocks|key|180199|text|我有以下错误，因为我错误地像这样声明了我的函数组件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|180200|async+functionName()+{
...
}
export+default+functionName|code-block|syntax|javascript|180201|我把它改成|180202|const+FunctionName+=+()+=>+{
...
}
export+default+FunctionName|180203|我希望它也适用于面临同样错误的人。|180204|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I had the following error because I declared my functional component like this by mistake.
<pre><code>async functionName() {
...
}
export default functionName
</code></pre>
I changed it to
<pre><code>const FunctionName = () =&gt; {
...
}
export default FunctionName
</code></pre>
I hope it would also work for someone who faces the same error.

blocks|key|182480|text|几天前我也遇到了同样的错误。我想澄清几点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|182481|182482|构建是根据浏览器的页面和URL进行的。如果你看到像|ordered-list-item|182483|这样的东西|182484|在以下路径上|182485|导出遇到错误:+/about|blockquote|182486|182487|182488|然后你应该复制"/about“并粘贴到当前url的前面，如下所示：|182489|182490|+http://localhost:3000/about|offset|length|182491|182492|182493|然后，您将看到错误或任何重大警告。解决它，你就准备好构建了。|182494|entityMap|0|LINK|mutability|MUTABLE|url|http://localhost:3000/about^0|0|0|0|0|0|0|0|0|0|0|1|R|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|19|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1A|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1B|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1C|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|R|3|S|5|L|7|1H|8|@]|9|@$T|1I|U|1J|1|1K]]|A|$]]|$1|V|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1N|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|10|$11|$5|12|13|14|A|$15|16]]]]

I ran into same error few days back.
few Points I would want to clarify.
<ol>
<li>Build happens as per the pages and URLs of the browser.
if you are seeing something like</li>
</ol>
<blockquote>
Export encountered errors on following paths:
/about
</blockquote>
Then you should copy &quot;/about&quot; and paste in front of the current url like:
<blockquote>
http://localhost:3000/about
</blockquote>
then you will see the error or any major warning.
resolve it, you are ready to Build.

blocks|key|2945105|text|在我的情况下，我只是安装"eslint“添加到我的脚本"lint":+"next+lint"然后我只是运行脚本输入"npm+run+lint”然后我选择"recommended"，安装后我再次运行脚本输入"npm+run+lint"，这一次它给我一个错误，说我应该降级"eslint“到”版本7“的好事情是他们已经给了"npm命令”，我应该输入降级版本，只要按照说明。然后再次运行"eslint“，直到”您在安装中看不到任何错误“。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2945106|然后运行"npm+run+build“，这将为您提供代码中所有错误的权威描述以及”构建过程失败“的原因。|BOLD|2945107|基于这些错误。我修复了以下问题。|2945108|my+pages文件夹中所有导出的组件应如下所示：|2945109|const+Home+=+()+=>+{
++return()
}
export+default+Home|code-block|syntax|javascript|2945110|不是这样的：|2945111|const+home+=+()+=>+{
++return()
}
export+default+home|2945112|我有未使用的import+{+useState+}+from+'react'，所以我删除了它。|2945113|我在about页面上有一个我从未使用过的道具。|2945114|const+About+=+(+{+listings+}+)+=>+{
++return()
}|2945115|我使用getStaticProps()从pages/api/mydata调用数据，所以我将其更改为getServerSideProps()|2945116|然后我再次尝试"npm+run+build“，这一次它没有给我任何错误，并且构建过程成功。|2945117|entityMap^0|R|J|1M|C|25|B|2V|C|0|5|D|Y|4|0|0|0|0|0|0|6|W|0|0|0|3|G|K|G|1D|K|0|8|D|0^^$0|@$1|2|3|4|5|6|7|17|8|@$9|18|A|19|B|C]|$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1G|8|@$9|1H|A|1I|B|C]|$9|1J|A|1K|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|1L|8|@]|D|@]|E|$]]|$1|K|3|L|5|6|7|1M|8|@]|D|@]|E|$]]|$1|M|3|N|5|O|7|1N|8|@]|D|@]|E|$P|Q]]|$1|R|3|S|5|6|7|1O|8|@]|D|@]|E|$]]|$1|T|3|U|5|O|7|1P|8|@]|D|@]|E|$P|Q]]|$1|V|3|W|5|6|7|1Q|8|@$9|1R|A|1S|B|C]]|D|@]|E|$]]|$1|X|3|Y|5|6|7|1T|8|@]|D|@]|E|$]]|$1|Z|3|10|5|O|7|1U|8|@]|D|@]|E|$P|Q]]|$1|11|3|12|5|6|7|1V|8|@$9|1W|A|1X|B|C]|$9|1Y|A|1Z|B|C]|$9|20|A|21|B|C]]|D|@]|E|$]]|$1|13|3|14|5|6|7|22|8|@$9|23|A|24|B|C]]|D|@]|E|$]]|$1|15|3|-4|5|6|7|25|8|@]|D|@]|E|$]]]|16|$]]

In my case I just install the &quot;eslint&quot; by adding this to my script <code>&quot;lint&quot;: &quot;next lint&quot;</code> then I just run the script by typing &quot;<code>npm run lint</code>&quot; then I select &quot;<code>recommended</code>&quot;, after installation I run the script again by typing &quot;<code>npm run lint</code>&quot;, this time it gave me an error saying that I should downgrade the &quot;eslint&quot; to &quot;version 7&quot; the good thing is they already gave the &quot;npm command&quot; that I should type to downgrade the version, just follow the description. then run the &quot;eslint&quot; again until &quot;you don't see any errors in the installation&quot;.
then run the &quot;<code>npm run build</code>&quot; this will give you a definitive description of all the errors in the code and why the &quot;build process is failed&quot;
based on the errors. I fixed the following.
all exported components in my pages folder should be like this:
<pre><code>const Home = () =&gt; {
 return()
}
export default Home
</code></pre>
not this:
<pre><code>const home = () =&gt; {
 return()
}
export default home
</code></pre>
I have unused <code>import { useState } from 'react'</code> so I remove it.
I have a prop on the about page that I never use.
<pre><code>const About = ( { listings } ) =&gt; {
 return()
}
</code></pre>
and I use the <code>getStaticProps()</code> to call data from <code>pages/api/mydata</code> so I change it to <code>getServerSideProps()</code>
then I try the &quot;<code>npm run build</code>&quot; again, this time it gave me no errors and the build process was successful.

blocks|key|182519|text|如果回退设置为true，则需要处理回退状态。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|182520|您需要添加|182521|if+(router.isFallback)+{
++++<h1>Data+is+loading</h1>;
}|code-block|syntax|javascript|182522|您可以在if语句体中放入任何内容，这将放入function组件中，如下所示|offset|length|style|CODE|182523|const+PostDetails+=+({+post+})+=>+{
++const+router+=+useRouter();

++if+(router.isFallback)+{
++++<h1>Data+is+loading</h1>;
++}

++return+(

)|182524|entityMap^0|0|0|0|4|2|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@$K|W|L|X|M|N]]|9|@]|A|$]]|$1|O|3|P|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

If your fallback is set to true you need to handle the fallback state.
You need to add
<pre><code>if (router.isFallback) {
 &lt;h1&gt;Data is loading&lt;/h1&gt;;
}
</code></pre>
You can put anything in the body of <code>if</code> statement, and this is going inside the function component like this
<pre><code>const PostDetails = ({ post }) =&gt; {
 const router = useRouter();

 if (router.isFallback) {
 &lt;h1&gt;Data is loading&lt;/h1&gt;;
 }

 return (

)
</code></pre>

blocks|key|180262|text|在我的例子中，当我重新连接到互联网并重新构建它时，互联网连接很低，它成功地构建了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|180263|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case there was a low internet connection when I reconnected to the internet and build it again, it was built successfully.

blocks|key|5058843|text|我的问题是，尽管路由存在，但它有一个错误，没有显示出来。在我使用MDX文件与next.js一起生成路由的情况下，其中一个MDX文件的属性/值是无效的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5058844|例如，如果MDX中包含以下内容：|5058845|---
slug:+test-mdx-post
title:+This+is+a+test+post
date:+2020-06-10
topics:
++-+stackoverflow
---|code-block|syntax|javascript|5058846|如果在其他地方分配的stackoverflow不是一个有效的主题，您将在您的/blog/test-mdx-post上获得错误Export+encountered+errors+on+following+paths:，或者无论您为该MDX指定的等价路由是什么。|offset|length|style|CODE|5058847|简而言之，检查您的MDX文件是否经过拼写检查，以及所有属性和值是否可用。|5058848|entityMap^0|0|0|0|A|D|12|J|1Q|19|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@$K|W|L|X|M|N]|$K|Y|L|Z|M|N]|$K|10|L|11|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|R|$]]

My problem was that route, while it existed, had an error in it that wasn't being shown. In my case where I have MDX files that are being used with next.js to generate routes, one of my MDX files had a property/value that was invalid.
For example, if you have the following in an MDX:
<pre><code>---
slug: test-mdx-post
title: This is a test post
date: 2020-06-10
topics:
 - stackoverflow
---
</code></pre>
If <code>stackoverflow</code> is not a valid topic assigned elsewhere, you'll get the error <code>Export encountered errors on following paths:</code> on your <code>/blog/test-mdx-post</code> or whatever your equivalent route is for that MDX.
In short, check that your MDX files are spell-checked and all properties and values are usable.

blocks|key|2945190|text|在我的例子中，这发生在后端API宕机的时候。因此您需要等到后台API重置后再重试|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2945191|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case this happened when backend API was down. So you need to wait till backend API will reset and try again

blocks|key|180284|text|删除节点模块并重新安装后，通过运行yarn+install，错误得到解决。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|180285|entityMap^0|H|C|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

After Deleting node modules and installing them again, by running <code>yarn install</code>, error got resolved.

blocks|key|180291|text|我得到了这个错误，我发现我无意中导入了useEffect依赖，如下所示|type|unstyled|depth|inlineStyleRanges|entityRanges|data|180292|import+{+useEffect+}+from+'react/cjs/react.development';|code-block|syntax|javascript|180293|有一次，我更新了它，并从'react‘导入了它。|180294|import+React,+{+useEffect+}+from+'react';|180295|我能够建立这个项目。|180296|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I got this error, I found out that I unintentionally imported useEffect dependency like this
<pre><code>import { useEffect } from 'react/cjs/react.development';
</code></pre>
Once, I updated it and imported it from 'react'.
<pre><code>import React, { useEffect } from 'react';
</code></pre>
I am able to build the project.

I am encountering this build error when I deploy my next js site to vercel
<pre><code>15:02:38 &gt; Build error occurred
15:02:38 Error: Export encountered errors on following paths:
15:02:38 /about/undefined
15:02:38 at exportApp (/vercel/workpath0/node_modules/next/dist/export/index.js:30:1103)
15:02:38 at processTicksAndRejections (internal/process/task_queues.js:97:5)
15:02:38 at async /vercel/workpath0/node_modules/next/dist/build/index.js:39:69
15:02:38 at async /vercel/workpath0/node_modules/next/dist/build/tracer.js:1:525
</code></pre>
My website does not have a page called about, so I really don't know what this error is referring to. I checked as much as I could to find a reliable answer, but couldn't. Any help is appreciated!

Next JS build failing due to ''Export encountered errors on following paths"

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

当我将我的下一个js站点部署到vercel时，我遇到了这个构建错误。15:02:38    > Build error occurred15:02:38    Error: Export encountered errors on following paths:15:02:38        /about/undefined15:02:38        at exportApp (/verce

问下一个JS构建失败，原因是‘’导出在以下路径上遇到错误“
EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问下一个JS构建失败，原因是‘’导出在以下路径上遇到错误“EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问下一个JS构建失败，原因是‘’导出在以下路径上遇到错误“
EN