-
-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: resolve nushell support issue #397
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #397 +/- ##
==========================================
- Coverage 28.89% 28.26% -0.63%
==========================================
Files 42 42
Lines 4122 4206 +84
==========================================
- Hits 1191 1189 -2
- Misses 2806 2892 +86
Partials 125 125 ☔ View full report in Codecov by Sentry. |
@colececil I didn't have any windows machine, could you test it in windows? it actually worked in mac: |
@bytemain Hmm, it still doesn't seem to be working for me in Windows. Here are the steps I followed:
After doing that, here's what I'm getting:
All the config stuff there looks right to me, but it's not using the nodejs version I told it to with |
Ok, here's some more info to go off of for debugging:
There are two things I'm not understanding:
|
I also reviewed your code changes in this pull request, and they made sense to me. The only thing I'm not understanding is what's in |
I'm currently on Chinese New Year holiday. I'll look into the bug as soon as I return. |
Enjoy! 🎉 |
@bytemain, did you ever get a chance to look at this again? |
Test vfox 0.6.1 on windows nushell, looks like it has some bug, I will try to resolve them in this weekend |
Thanks - let me know if I can assist in any way! |
fixed in #412 The reason is when we finished switch to another version, and the because so the fix is let ![]() |
No description provided.