remilia/jinshen-website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[BUG] 客户端无法正常获取传入的环境变量 #33

New Issue
Closed
opened 2025-09-27 13:59:41 +08:00 by remilia · 2 comments
remilia commented 2025-09-27 13:59:41 +08:00
Owner
Copy Link

问题概述/Summary

客户端无法正常获取传入的环境变量

重现步骤/Steps to Reproduce

执行构建版本，通过NUXT_PUBLIC_STRAPI_URL=<CMS_URL>传入后端CMS的地址，通过前端地址访问站点，查看首页是否正确渲染

预期结果/Expected Behavior

首页正确渲染

实际结果/Actual Behavior

首页无法正确渲染

环境信息/Environment

No response

检查表/Checklist

  • 已搜索过类似问题，确保不是重复报告
  • 提供了足够的信息以帮助我们理解和重现问题
  • 如果可能，已附上相关截图或日志文件
### 问题概述/Summary 客户端无法正常获取传入的环境变量 ### 重现步骤/Steps to Reproduce 执行构建版本，通过NUXT_PUBLIC_STRAPI_URL=<CMS_URL>传入后端CMS的地址，通过前端地址访问站点，查看首页是否正确渲染 ### 预期结果/Expected Behavior 首页正确渲染 ### 实际结果/Actual Behavior 首页无法正确渲染 ### 环境信息/Environment _No response_ ### 检查表/Checklist - [x] 已搜索过类似问题，确保不是重复报告 - [x] 提供了足够的信息以帮助我们理解和重现问题 - [x] 如果可能，已附上相关截图或日志文件
remilia added the
Kind/Bug
 label 2025-09-27 13:59:41 +08:00
remilia commented 2025-09-27 14:11:20 +08:00
Author
Owner
Copy Link

Nuxt的预渲染机制会导致项目在构建时预先完成静态网页的渲染，此时runtimeConfig会被直接写入静态页面中，导致客户端页面无法正常获取传入的环境变量。
目前的项目为客户端从后端获取资源并与前端通信，如果改成服务端渲染SSR，则可能避免这个问题

Nuxt的预渲染机制会导致项目在构建时预先完成静态网页的渲染，此时runtimeConfig会被直接写入静态页面中，导致客户端页面无法正常获取传入的环境变量。 目前的项目为客户端从后端获取资源并与前端通信，如果改成服务端渲染`SSR`，则可能避免这个问题
remilia changed title from [BUG] 前端无法正常获取传入的环境变量 to [BUG] 客户端无法正常获取传入的环境变量 2025-09-27 14:11:36 +08:00
remilia commented 2025-09-27 14:13:32 +08:00
Author
Owner
Copy Link

考虑暂时禁用预渲染，并准备将客户端渲染改为服务端渲染

考虑暂时禁用预渲染，并准备将客户端渲染改为服务端渲染
remilia reopened this issue 2025-09-27 16:34:51 +08:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Kind/Bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
remilia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: remilia/jinshen-website#33
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?