langgenius/webapp-text-generator

webapp-text-generator's Issues

Is it safe to use NEXT_PUBLIC_APP_KEY for storing an API key?

As far as I know, the NEXT_PUBLIC_ prefix is typically used for non-sensitive environment variables.

If you use this prefix to store an API key, there is a chance that it could be leaked, right?

Docker build error

webapp-text-generator/app/api/parameters/route.ts Missing exception capture

The page you are trying to access is unavailable.

After cloning the repository, I only added the APP_ID and API_KEY fields, and then executed yarn dev. I encountered the following error message:

    data: {
      code: 'unauthorized',
      message: "The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn't understand how to supply the credentials required.",
      status: 401
    }

The page error is as follows:

firefox 低版本52.0.2(32位)无法打开页面

firefox版本：52.0.2 32位 2017.3月份版本
它会使用polyfills-xxxxx.js文件，是不是不支持HTML5的fetch特性呢？

现象就是，页面一直在loading等待，无法显示main页面内容。

The project is missing a Dockerfile file

The project is missing a Dockerfile file

build error

Build error on vercel

Error occurred prerendering page "/api/parameters". Read more: https://nextjs.org/docs/messages/prerender-error
AggregateError

local build can replicate this error.

部署后，没有输入框。完全不对

部署到vercel 上报错

输入问题，点击运行之后，右侧不会显示任何回答信息。

vercel报错信息如下：
error - TypeError: This ReadableStream did not return bytes.
at consumeUint8ArrayReadableStream (/var/task/node_modules/next/dist/compiled/edge-runtime/index.js:1:13979)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async sendResponse (/var/task/node_modules/next/dist/server/future/route-handlers/app-route-route-handler.js:128:34)
at async AppRouteRouteHandler.handle (/var/task/node_modules/next/dist/server/future/route-handlers/app-route-route-handler.js:415:13)
at async RouteHandlerManager.handle (/var/task/node_modules/next/dist/server/future/route-handler-managers/route-handler-manager.js:16:24)
at async doRender (/var/task/node_modules/next/dist/server/base-server.js:744:32)
at async cacheEntry1.responseCache.get.incrementalCache.incrementalCache (/var/task/node_modules/next/dist/server/base-server.js:931:28)
at async /var/task/node_modules/next/dist/server/response-cache/index.js:83:36

答案内容展示的时候，内容重复展示问题

后端返回的流式数据 是增量的 ，前端处理字符串的时候拿最后一个结果就行了。 目前 join字符串的方式会导致显示内容重复

更改后的代码