blocks|key|1671316|text|如果使用的是纱线3，则需要按照以下步骤设置VSCode：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1671317|运行yarn+dlx+@yarnpkg/sdks+vscode|unordered-list-item|offset|length|style|CODE|1671318|打开任何TypeScript文件|1671319|按ctrl%2Bshift%2Bp|1671320|选择“选择TypeScript版本”|1671321|选择“使用工作区版本”|1671322|其他编辑器的在这里读|1671323|entityMap|0|LINK|mutability|MUTABLE|url|https://yarnpkg.com/getting-started/editor-sdks#editor-setup^0|0|2|T|0|4|A|0|1|C|0|0|0|6|4|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@$E|12|F|13|G|H]]|9|@]|A|$]]|$1|I|3|J|5|D|7|14|8|@$E|15|F|16|G|H]]|9|@]|A|$]]|$1|K|3|L|5|D|7|17|8|@$E|18|F|19|G|H]]|9|@]|A|$]]|$1|M|3|N|5|D|7|1A|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1B|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1C|8|@]|9|@$E|1D|F|1E|1|1F]]|A|$]]|$1|S|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

If you're using yarn 3, then you need to follow those steps to set up your VSCode:
<ul>
<li>Run <code>yarn dlx @yarnpkg/sdks vscode</code></li>
<li>Open any <code>TypeScript</code> file</li>
<li>Press <code>ctrl+shift+p</code></li>
<li>Choose &quot;Select TypeScript Version&quot;</li>
<li>Pick &quot;Use Workspace Version&quot;</li>
</ul>
<a href="https://yarnpkg.com/getting-started/editor-sdks#editor-setup" rel="noreferrer">Read here</a> for other editors

blocks|key|676377|text|也许重新启动TS服务器就可以工作了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|676378|VsCode|offset|length|style|BOLD|676379|类型：ctrl+%2B+shift+%2B+p|CODE|676380|选择：>+TypeScript:+Restart+TS+server|676381|entityMap^0|0|0|6|0|3|G|0|3|V|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|S|8|@$D|T|E|U|F|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|V|8|@$D|W|E|X|F|J]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|N|$]]

Maybe just restarting the TS server can work.
VsCode
type: <code>ctrl + shift + p</code>
choose: <code>&gt; TypeScript: Restart TS server</code>

blocks|key|676447|text|我尝试了Cuong+Vu和其他许多人提出的解决方案，但没有奏效。对我来说，有效的是以下解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|676448|在Yarn+2/3中，由于node_modules文件夹中的PnP，对模块的支持被删除。按照下面的步骤解决问题。|676449|在项目根目录中创建.yarnrc.yml文件，|ordered-list-item|offset|length|style|CODE|676450|在文件nodeLinker:+node-modules中插入。|676451|在终端中运行命令yarn以重新创建node_modules文件夹。|676452|按照所有三个步骤，问题将得到解决。|676453|entityMap^0|0|0|9|B|0|3|O|0|8|4|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|@$G|V|H|W|I|J]]|9|@]|A|$]]|$1|K|3|L|5|F|7|X|8|@$G|Y|H|Z|I|J]]|9|@]|A|$]]|$1|M|3|N|5|F|7|10|8|@$G|11|H|12|I|J]]|9|@]|A|$]]|$1|O|3|P|5|6|7|13|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|R|$]]

I tried solution suggested by Cuong Vu and many others and it didn't work. For me what worked was the following solution:
In Yarn 2/3, support for modules in the node_modules folder is removed because of PnP. Follow the steps below to resolve the issue.
<ol>
<li>Create a <code>.yarnrc.yml</code> file in the project root,</li>
<li>Insert in the file <code>nodeLinker: node-modules</code>.</li>
<li>Run the command <code>yarn</code> in the terminal to recreate the node_modules folder.</li>
</ol>
Following all 3 steps the problem will be solved.

blocks|key|676478|text|在尝试其他解决方案之前：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|676479|再次检查您有一个node_modules文件夹|ordered-list-item|offset|length|style|CODE|676480|如果没有，运行yarn+(或npm+i)来安装模块|676481|意外删除node_modules文件夹是对TS2307+Cannot+find+module+''错误的最简单解释。|676482|它也得到OP注释的支持。|676483|“我没有node_module文件夹，只有.yarn和yarn.lock”|blockquote|676484|h/t+@geisterfurz007+007的评论。|676485|entityMap^0|0|8|C|0|7|4|E|5|0|L|S|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|W|8|@$E|X|F|Y|G|H]]|9|@]|A|$]]|$1|I|3|J|5|D|7|Z|8|@$E|10|F|11|G|H]|$E|12|F|13|G|H]]|9|@]|A|$]]|$1|K|3|L|5|6|7|14|8|@$E|15|F|16|G|H]]|9|@]|A|$]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|18|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|19|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|U|$]]

Before attempting other solutions:
<ol>
<li>Double check you have a <code>node_modules</code> folder</li>
<li>If not, run <code>yarn</code> (or <code>npm i</code>) to (re)install the modules</li>
</ol>
Accidentally deleting the node_modules folder is the simplest explanation for the <code>TS2307 Cannot find module ''</code> error.
It's also supported by OP comments
<blockquote>
&quot;i don't have node_module folder. Only .yarn and yarn.lock&quot;
</blockquote>
h/t @geisterfurz007's comments.

blocks|key|1108168|text|我想提供更多的背景和更多的笔记，其他人可能会欣赏他们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1108169|只要重读@Vagnerlandio+Nunes的答案，就可以了。问题解决了！|ordered-list-item|1108170|Recap/解决方案2:我只是使用npx+create-next-app引导一个新项目，遵循Next.js‘文档+with+npx+create-next-app@latest+--typescript+(使用yarn)或运行yarn+create+next-app+--typescript。我发现了与ts(2307):+Cannot+find+module+'next/app'+or+its+corresponding+type+declarations.相关的错误|offset|length|style|CODE|1108171|有了@warfield的回答，我注意到由于某种原因我没有node_modules文件夹，而且即使在运行yarn之后也没有创建它。我不得不运行npm+i来创建node_modules文件夹，尽管我计划使用yarn。|1108172|这是我运行yarn时得到的日志。|1108173|%25+yarn
➤+YN0000:+┌+Resolution+step
➤+YN0000:+└+Completed
➤+YN0000:+┌+Fetch+step
➤+YN0000:+└+Completed
➤+YN0000:+┌+Link+step
➤+YN0000:+│+ESM+support+for+PnP+uses+the+experimental+loader+API+and+is+therefore+experimental
➤+YN0000:+└+Completed
➤+YN0000:+Done+with+warnings+in+0s+244ms|code-block|syntax|javascript|1108174|这是我运行npm+i时得到的日志。|1108175|%25+npm+i++

added+235+packages,+and+audited+236+packages+in+10s

78+packages+are+looking+for+funding
++run+`npm+fund`+for+details

found+0+vulnerabilities|1108176|现在问题解决了，错误信息也消失了！|1108177|但是出于好奇，我再次运行了yarn，这是结果输出。|1108178|%25+yarn
➤+YN0070:+Migrating+from+Yarn+1;+automatically+enabling+the+compatibility+node-modules+linker+

➤+YN0000:+┌+Resolution+step
➤+YN0000:+└+Completed+in+3s+864ms
➤+YN0000:+┌+Fetch+step
➤+YN0013:+│+word-wrap@npm:1.2.3+can't+be+found+in+the+cache+and+will+be+fetched+from+the+remote+registry
➤+YN0013:+│+wrappy@npm:1.0.2+can't+be+found+in+the+cache+and+will+be+fetched+from+the+remote+registry
➤+YN0013:+│+yallist@npm:4.0.0+can't+be+found+in+the+cache+and+will+be+fetched+from+the+remote+registry
➤+YN0013:+│+yocto-queue@npm:0.1.0+can't+be+found+in+the+cache+and+will+be+fetched+from+the+remote+registry
➤+YN0019:+│+ms-npm-2.1.3-81ff3cfac1-aa92de6080.zip+appears+to+be+unused+-+removing
➤+YN0000:+└+Completed+in+0s+303ms
➤+YN0000:+┌+Link+step
➤+YN0007:+│+core-js-pure@npm:3.25.5+must+be+built+because+it+never+has+been+before+or+the+last+one+failed
➤+YN0000:+└+Completed+in+4s+288ms
➤+YN0000:+Done+in+8s+486ms|1108179|此外，如果你像我一样，你试图修改你的tsconfig.json文件|1108180|...
++"include":+[
++++"next-env.d.ts",
++++"**/*.ts",
++++"**/*.tsx"
++],
...|1108181|至|1108182|...
"include":+[
++++"next-env.d.ts",
++++"pages/**/*",
++++"src/**/*",
],
...|1108183|因为你认为基于这个GitHub+评论会有所帮助。现在您将看到一个新的错误消息ts(2686):+'React'+refers+to+a+UMD+global,+but+the+current+file+is+a+module.+Consider+adding+an+import+instead.。如果您只执行上述步骤，这是不必要的。所以我就把它改回来了。|1108184|将tsconfig.json的"compilerOptions":+{+...+}从"jsx":+"preserve"更改为"jsx":+"react-jsx"也是不必要的(对另一个尝试解决方案的引用)。|1108185|在任何时候，如果您想确保您所做的更改(对于tsconfig)已经生效，请尝试命令%2B+shift+%2B+p并输入>+TypeScript:+Restart+TS+server，您应该会看到一些更新。|BOLD|1108186|entityMap|0|LINK|mutability|MUTABLE|url|https://nextjs.org/docs/getting-started|1|https://github.com/vercel/next.js/discussions/19891|2|https://bobbyhadz.com/blog/react-typescript-cannot-find-name#:%257E:text=To%2520solve%2520the%2520%2522Cannot%2520find,types%2520packages%2520for%2520your%2520application.^0|0|0|H|J|1Q|13|2X|4|35|X|48|27|1I|2|0|0|S|C|1F|4|1Y|5|26|C|2T|4|0|5|4|0|0|5|5|0|0|0|D|4|0|0|I|D|0|0|0|0|12|32|G|2|1|0|1|D|F|Q|16|H|1Q|I|2F|D|2|0|12|D|1I|V|0^^$0|@$1|2|3|4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1V|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|1W|8|@$G|1X|H|1Y|I|J]|$G|1Z|H|20|I|J]|$G|21|H|22|I|J]|$G|23|H|24|I|J]|$G|25|H|26|I|J]]|9|@$G|27|H|28|1|29]]|A|$]]|$1|K|3|L|5|D|7|2A|8|@$G|2B|H|2C|I|J]|$G|2D|H|2E|I|J]|$G|2F|H|2G|I|J]|$G|2H|H|2I|I|J]|$G|2J|H|2K|I|J]]|9|@]|A|$]]|$1|M|3|N|5|6|7|2L|8|@$G|2M|H|2N|I|J]]|9|@]|A|$]]|$1|O|3|P|5|Q|7|2O|8|@]|9|@]|A|$R|S]]|$1|T|3|U|5|6|7|2P|8|@$G|2Q|H|2R|I|J]]|9|@]|A|$]]|$1|V|3|W|5|Q|7|2S|8|@]|9|@]|A|$R|S]]|$1|X|3|Y|5|6|7|2T|8|@]|9|@]|A|$]]|$1|Z|3|10|5|D|7|2U|8|@$G|2V|H|2W|I|J]]|9|@]|A|$]]|$1|11|3|12|5|Q|7|2X|8|@]|9|@]|A|$R|S]]|$1|13|3|14|5|D|7|2Y|8|@$G|2Z|H|30|I|J]]|9|@]|A|$]]|$1|15|3|16|5|Q|7|31|8|@]|9|@]|A|$R|S]]|$1|17|3|18|5|6|7|32|8|@]|9|@]|A|$]]|$1|19|3|1A|5|Q|7|33|8|@]|9|@]|A|$R|S]]|$1|1B|3|1C|5|6|7|34|8|@$G|35|H|36|I|J]]|9|@$G|37|H|38|1|39]]|A|$]]|$1|1D|3|1E|5|D|7|3A|8|@$G|3B|H|3C|I|J]|$G|3D|H|3E|I|J]|$G|3F|H|3G|I|J]|$G|3H|H|3I|I|J]]|9|@$G|3J|H|3K|1|3L]]|A|$]]|$1|1F|3|1G|5|D|7|3M|8|@$G|3N|H|3O|I|1H]|$G|3P|H|3Q|I|J]]|9|@]|A|$]]|$1|1I|3|-4|5|6|7|3R|8|@]|9|@]|A|$]]]|1J|$1K|$5|1L|1M|1N|A|$1O|1P]]|1Q|$5|1L|1M|1N|A|$1O|1R]]|1S|$5|1L|1M|1N|A|$1O|1T]]]]

I wanted to provide more context and additional notes for others who might appreciate them.
<ol start="0">
<li>Just reread @Vagnerlandio Nunes's answer, and it was spot on. Problem solved!
</li>
<li>Recap/Solution #2: I was simply bootstrapping a new project using <code>npx create-next-app</code>, following the Next.js' <a href="https://nextjs.org/docs/getting-started" rel="nofollow noreferrer">documentation</a> with <code>npx create-next-app@latest --typescript</code> (using <code>yarn</code>) or ran <code>yarn create next-app --typescript</code>. I got errors relating to <code>ts(2307): Cannot find module 'next/app' or its corresponding type declarations.</code>
</li>
<li>With @warfield's answer, I noticed I did not have a <code>node_modules</code> folder for some reason, and it was not created even after I ran <code>yarn</code>. I had to run <code>npm i</code> to create the <code>node_modules</code> folder, even though I planned to use <code>yarn</code>.
</li>
</ol>
This is the log I got when I ran <code>yarn</code>.
<pre><code>% yarn
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed
➤ YN0000: ┌ Link step
➤ YN0000: │ ESM support for PnP uses the experimental loader API and is therefore experimental
➤ YN0000: └ Completed
➤ YN0000: Done with warnings in 0s 244ms
</code></pre>
This is the log I got when I ran <code>npm i</code>.
<pre><code>% npm i 

added 235 packages, and audited 236 packages in 10s

78 packages are looking for funding
 run `npm fund` for details

found 0 vulnerabilities
</code></pre>
Now the problem is solved, and the error messages have gone away!
<ol start="3">
<li>But out of curiosity, I ran <code>yarn</code> again, and this is the resulting output.</li>
</ol>
<pre><code>% yarn
➤ YN0070: Migrating from Yarn 1; automatically enabling the compatibility node-modules linker 

➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 3s 864ms
➤ YN0000: ┌ Fetch step
➤ YN0013: │ word-wrap@npm:1.2.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrappy@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yallist@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yocto-queue@npm:0.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0019: │ ms-npm-2.1.3-81ff3cfac1-aa92de6080.zip appears to be unused - removing
➤ YN0000: └ Completed in 0s 303ms
➤ YN0000: ┌ Link step
➤ YN0007: │ core-js-pure@npm:3.25.5 must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 4s 288ms
➤ YN0000: Done in 8s 486ms
</code></pre>
<ol start="4">
<li>In addition, if you're like me, you tried to modify your <code>tsconfig.json</code> file from</li>
</ol>
<pre><code>...
 &quot;include&quot;: [
 &quot;next-env.d.ts&quot;,
 &quot;**/*.ts&quot;,
 &quot;**/*.tsx&quot;
 ],
...
</code></pre>
to
<pre><code>...
&quot;include&quot;: [
 &quot;next-env.d.ts&quot;,
 &quot;pages/**/*&quot;,
 &quot;src/**/*&quot;,
],
...
</code></pre>
because you thought it was going to help based on this GitHub <a href="https://github.com/vercel/next.js/discussions/19891" rel="nofollow noreferrer">comment</a>. You would now be seeing a new error message <code>ts(2686): 'React' refers to a UMD global, but the current file is a module. Consider adding an import instead.</code>. This is not necessary if you simply did the above step. So I just changed it back.
<ol start="5">
<li>Changing your <code>tsconfig.json</code>'s <code>&quot;compilerOptions&quot;: { ... }</code> from <code>&quot;jsx&quot;: &quot;preserve&quot;</code> to <code>&quot;jsx&quot;: &quot;react-jsx&quot;</code> is also not necessary (<a href="https://bobbyhadz.com/blog/react-typescript-cannot-find-name#:%7E:text=To%20solve%20the%20%22Cannot%20find,types%20packages%20for%20your%20application." rel="nofollow noreferrer">reference to another attempted solution</a>).</li>
</ol>
<ol start="6">
<li>At any point if you want to make sure that the changes you've made (in regards to tsconfig) has gone into effect, try command + shift + p and enter <code>&gt; TypeScript: Restart TS server</code>, and you should see some refreshing going on.</li>
</ol>

blocks|key|1108097|text|我将它添加到我的tsconfig.json文件中--我可以看到您已经拥有它了，但它不是我的解决方案的一部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1108098|"moduleResolution":+"node",|code-block|syntax|javascript|1108099|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|$]]

I added this to my tsconfig.json file
I can see you have it already, but it was not part of my solution
<pre><code>&quot;moduleResolution&quot;: &quot;node&quot;,
</code></pre>

Getting <code>Cannot find module '' or its corresponding type declarations.</code> when importing in Next.js project.
This happens on every single import. <a href="https://i.stack.imgur.com/TIW1b.png" rel="noreferrer">Preview</a>
Yarn version : 3.1.0-rc.2 
Next version: 11.1.2
tsconfig.json:
<pre><code>{
 &quot;compilerOptions&quot;: {
 &quot;target&quot;: &quot;es6&quot;,
 &quot;lib&quot;: [
 &quot;dom&quot;,
 &quot;dom.iterable&quot;,
 &quot;esnext&quot;
 ],
 &quot;allowJs&quot;: true,
 &quot;skipLibCheck&quot;: true,
 &quot;strict&quot;: true,
 &quot;forceConsistentCasingInFileNames&quot;: true,
 &quot;noEmit&quot;: true,
 &quot;esModuleInterop&quot;: true,
 &quot;module&quot;: &quot;esnext&quot;,
 &quot;moduleResolution&quot;: &quot;node&quot;,
 &quot;experimentalDecorators&quot;: true,
 &quot;resolveJsonModule&quot;: true,
 &quot;isolatedModules&quot;: true,
 &quot;importHelpers&quot;: true,
 &quot;jsx&quot;: &quot;preserve&quot;,
 // &quot;baseUrl&quot;: &quot;src&quot;
 },
 &quot;include&quot;: [
 &quot;next-env.d.ts&quot;,
 &quot;**/*.ts&quot;,
 &quot;**/*.tsx&quot;
 ],
 &quot;exclude&quot;: [
 &quot;node_modules&quot;
 ],
}
</code></pre>

Cannot find module 'next' or its corresponding type declarations

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

在导入Cannot find module '' or its corresponding type declarations.项目时获取Next.js。每个导入都会发生这种情况。纱线版本: 3.1.0-rc.2下一版本: 11.1.2tsconfig.json:{  "compilerOptions": {    "target": "es6",    "lib": [      "dom", 

问无法找到模块“next”或其相应的类型声明
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法找到模块“next”或其相应的类型声明EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法找到模块“next”或其相应的类型声明
EN