-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[BUG] npx fcy
#7974
Comments
ehm...the problem seems to happen only in visual studio code built-in powershell terminal
|
@lorypelli We have gone through the issue u mention we are not able to see expected behaviour which u mentioned there is an issue from npx fcy@1.1.17.please provide valid information or steps to reproduce the issue. i have attached a file please go through it. |
It happens with windows powershell and on visual studio code only |
You would need to use Windows to replicate |
Any updates? |
new version I just published seems to work, the other was removed, versioning is not important in this package so I keep only the latest one... |
any idea of why that happened? |
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
using a specific version (1.1.17) fails while using latest doesn't fail
Expected Behavior
it should work...
Steps To Reproduce
try using
npx fcy@1.1.17
and after thatnpx fcy@latest
both on windows powershellEnvironment
The text was updated successfully, but these errors were encountered: