langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Enhance npm Start Script for Windows Compatibility #2184

New Issue
Closed
opened 2026-02-21 17:42:40 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:42:40 -05:00
Owner
Copy Link
Copy Source

Originally created by @chiragksharma on GitHub (Apr 13, 2024).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • Pleas do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

Yes, the current npm start script utilizes commands that are not compatible with Windows environments, specifically the Unix cp command. This results in errors like 'cp' is not recognized as an internal or external command, operable program or batch file. when developers on Windows attempt to run the script.

2. Describe the feature you'd like to see

I propose to modify the npm start script to use cross-platform compatible commands, ensuring it runs smoothly on both Windows and Unix-like systems. This involves replacing Unix-specific commands with the shx command utility, which mimics Unix commands in a cross-platform way.

3. How will this feature improve your workflow or experience?

  1. Eliminate OS-specific errors
  2. Standardize development practices
  3. Reduce setup time and confusion

4. Additional context or comments

Modify the start Script

Update the start script in package.json to use shx for the copy operations. Here’s how you can modify it:

{
  "scripts": {
    "start": "shx cp -r .next/static .next/standalone/.next/static && shx cp -r public .next/standalone/public && cross-env PORT=$npm_config_port HOSTNAME=$npm_config_host node .next/standalone/server.js"
  }
}

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @chiragksharma on GitHub (Apr 13, 2024). ### Self Checks - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] Pleas do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Yes, the current `npm start` script utilizes commands that are not compatible with Windows environments, specifically the `Unix cp command`. This results in errors like '`cp`' is not recognized as an internal or external command, operable program or batch file. when developers on Windows attempt to run the script. ### 2. Describe the feature you'd like to see I propose to modify the npm start script to use cross-platform compatible commands, ensuring it runs smoothly on both Windows and Unix-like systems. This involves replacing Unix-specific commands with the shx command utility, which mimics Unix commands in a cross-platform way. ### 3. How will this feature improve your workflow or experience? 1. Eliminate OS-specific errors 2. Standardize development practices 3. Reduce setup time and confusion ### 4. Additional context or comments **Modify the start Script** Update the start script in package.json to use shx for the copy operations. Here’s how you can modify it: ``` { "scripts": { "start": "shx cp -r .next/static .next/standalone/.next/static && shx cp -r public .next/standalone/public && cross-env PORT=$npm_config_port HOSTNAME=$npm_config_host node .next/standalone/server.js" } } ``` ### 5. Can you help us with this feature? - [X] I am interested in contributing to this feature.
yindo added the 💪 enhancementgood first issue labels 2026-02-21 17:42:40 -05:00
yindo closed this issue 2026-02-21 17:42:40 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label good first issue 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#2184
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?