[Form] 组件在 Nuxt3 build 时报错：The symbol "isError" has already been declared

[miswanting]

tdesign-vue-next 版本

1.7.1

重现链接

https://github.com/miswanting/nuxt3-build-tdesign-iserror-already-been-declared-bug
更加精准的重现：https://codesandbox.io/p/devbox/nuxt3-build-tdesign-vue-next-iserror-already-been-declared-bug-f8ql3d

重现步骤

pnpm i
pnpm nuxt build

期望结果

编译无错误

实际结果

编译中断，报错：

 ERROR  Error: Transform failed with 1 error:                 nitro 2:21:03 AM
/workspaces/sandbox/.nuxt/dist/server/_nuxt/index-e3e9d414.js:4312:170: ERROR: The symbol "isError" has already been declared


The symbol "isError" has already been declared


 ERROR  Transform failed with 1 error:                              2:21:03 AM
/workspaces/sandbox/.nuxt/dist/server/_nuxt/index-e3e9d414.js:4312:170: ERROR: The symbol "isError" has already been declared

  .nuxt/dist/server/_nuxt/index-e3e9d414.js:4312:170: ERROR: The symbol "isError" has already been declared
  at failureErrorWithLog (node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:1650:15)
  at node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:848:29
  at responseCallbacks.<computed> (node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:703:9)
  at handleIncomingPacket (node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:763:9)
  at Socket.readFromStdout (node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:679:7)
  at Socket.emit (node:events:514:28)
  at addChunk (node:internal/streams/readable:376:12)
  at readableAddChunk (node:internal/streams/readable:349:9)
  at Readable.push (node:internal/streams/readable:286:10)
  at Pipe.onStreamRead (node:internal/stream_base_commons:190:23) 



 ERROR  Transform failed with 1 error:                              2:21:03 AM
/workspaces/sandbox/.nuxt/dist/server/_nuxt/index-e3e9d414.js:4312:170: ERROR: The symbol "isError" has already been declared

 ELIFECYCLE  Command failed with exit code 1.

框架版本

Nuxt(3.8.1)

浏览器版本

No response

系统版本

No response

Node版本

20.5.1

补充说明

• dev模式时无报错；
• 仅有pages/目录中的文件会出现该报错，app.vue中不会出现这个问题；
• 该bug确认到两个症状：
  1. Bug 1：直接使用Form组件会报错；【该Bug可用ClientOnly绕过】
  2. Bug 2：在Layout组件中使用Form组件会报错；【该Bug不可用ClientOnly绕过】
• 该bug影响很大，导致tdsign-vue-next几乎无法在Nuxt3框架中完成构建和发布。

[github-actions]

👋 @miswanting，感谢给 TDesign 提出了 issue。
请根据 issue 模版确保背景信息的完善，我们将调查并尽快回复你。

[wangzhishou]

我也复现了这个问题，简直没办法用啊，

补充说明
dev模式时无问题

[wangzhishou]

<template><t-form> </t-form></template>

直接这样build就报错，是t-form的锅

[wangzhishou]

实测在包含t-form组件的页面，preRender时候报错，可以外加<client-only>包裹先避免。

[miswanting]

更新：v1.7.1依然存在这个问题。

存在两类Bug，其中一个可用ClientOnly组件绕过，但另一个无法用该方法绕过。【相关信息已在原文中更新，并附上了精简版重现链接】

Bug 1：/pages/bug-1.vue

<template>
  <!-- 使用 ClientOnly **可绕过**该问题 -->
  <!-- <ClientOnly> -->
  <TForm></TForm>
  <!-- </ClientOnly> -->
</template>

Bug 2：/pages/bug-2.vue

<template>
  <TLayout>
    <!-- 使用 ClientOnly **不可绕过**该Bug -->
    <ClientOnly>
      <TForm></TForm>
    </ClientOnly>
  </TLayout>
</template>

[github-actions]

♥️ 有劳 @LeeJim @PengYYYYY @k1nz 尽快确认问题。
确认有效后将下一步计划和可能需要的时间回复给 @miswanting 。

[github-actions]

♥️ 有劳 @LeeJim @PengYYYYY @k1nz 尽快确认问题。
确认有效后将下一步计划和可能需要的时间回复给 @miswanting 。

[uyarn]

问题已修复 下个版本带上 thanks @richardji202 🌹

[uyarn]

fixed 1.9.0