mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #4907] [bug]: Can't build/start 2025.2.2 due to error while pnpm run generate #1851
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#1851
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 @LordSimal on GitHub (Mar 18, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4907
Is there an existing issue for this?
Current behavior
I tried to upgrade my self hosted AIO instance from 2025.2.1 to 2025.2.2 and now I get the following error:
Steps to reproduce
Here is basically what I did to "properly" stop the existing instance and upgrade to the newest version:
Logs and Screenshots
Environment
Production
Hoppscotch Version
Self-hosted
Interceptor
Not Applicable - Issue not related to network requests
Browsers Affected
No response
Operating System
Linux
Additional Information
No response
@LordSimal commented on GitHub (Mar 18, 2025):
Not directly the same issue but could be related to https://github.com/hoppscotch/hoppscotch/issues/4902 as well
@517feng commented on GitHub (Mar 19, 2025):
yes,exec docker compose --profile default up -d resulted in the same error message
@LordSimal commented on GitHub (Mar 19, 2025):
The weird thing is the fact, that even going back to 2025.2.1 doesn't fix the problem.
Smells to me like some JS Dependency 💩
@LordSimal commented on GitHub (Mar 19, 2025):
Sorry to directly ping @CuriousCorrelation but this is a rather pressing issue since - well - the instance is completely down and no one of my team can access the configured HTTP requests 😅
@LordSimal commented on GitHub (Mar 19, 2025):
To be more exact, the only difference between the default docker-compose.yml and my file is the following:
@jamesgeorge007 commented on GitHub (Mar 19, 2025):
Hi, we've identified the root cause of this issue propagating from the dependency chain. It'll be addressed in the upcoming patch release.
@LordSimal commented on GitHub (Mar 19, 2025):
2025.2.3 fixes this problem, thank you for the quick resolution 🙇🏻