mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #3289] [bug]: Hoppscotch CLI error #1088
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#1088
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 @SaailN on GitHub (Aug 24, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3289
Is there an existing issue for this?
Current behavior
I was exploring
hopp testcommand to run the collection file(.json) exported from hoppscotch.io but getting the following error while running the file.Steps to reproduce
Environment
Production
Version
Cloud
@nivedin commented on GitHub (Sep 18, 2023):
@SaailN can you try renaming the file name and run the test.
@AndrewBastin commented on GitHub (Sep 18, 2023):
@SaailN can we also get your node version and OS info ?
@KrystianDziedziola commented on GitHub (Dec 21, 2023):
I had a similar problem and using the latest Node version fixed it.
I was using an old version of the Node because of the requirements of a project. If you're in a similar situation, you can use nvm to keep multiple versions of the Node.
@jamesgeorge007 commented on GitHub (Apr 10, 2024):
@SaailN, can you try with the latest version of the CLI? Please ensure the Node.js version is at least
v18.@joeljstephen commented on GitHub (Apr 18, 2024):
@SaailN I will be closing this issue. If you still face the issue on the latest builds, please feel free to reopen the issue.