mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #5396] [bug]: unable to build backend on 2025.8.1 on Github CI #2073
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#2073
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @Leon-Luu on GitHub (Sep 22, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5396
Originally assigned to: @Leon-Luu on GitHub.
Is there an existing issue for this?
Platform
Web App
Browser
Chrome
Operating System
Linux
Bug Description
When building the Hoppscotch backend Docker image using Alpine as the base, the build fails with the error /bin/sh: npm: not found.
This is because the Alpine nodejs package does not include npm by default, but the Dockerfile expects npm to be available for global installs.
Steps to Reproduce:
Clone the Hoppscotch repository.
Run docker build -t hoppscotch-backend -f prod.Dockerfile
Observe the build failure at the step running npm install -g ....
Deployment Type
Self-hosted (on-prem deployment)
Version
2025.8.1
@Leon-Luu commented on GitHub (Sep 22, 2025):
@jamesgeorge007 please check, I have fix propose to https://github.com/hoppscotch/hoppscotch/pull/5397
@jamesgeorge007 commented on GitHub (Sep 25, 2025):
Closing, since this is now resolved. Thanks for the PR, @Leon-Luu 🙌