-
-
Notifications
You must be signed in to change notification settings - Fork 272
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
0.17.0-beta.28 dl-loader TypeError (windows 10) #2064
Comments
Any chance you could add a console.log to C:\nodejs\node_modules\jspm\node_modules\jspm-github\github.js:81:16 to see what the value of //cc @tamird |
found where it's writing the file: after I set the registry, I'm not getting the error anymore. not sure if relevant, but the
it seems that upgrading windows 10 to the "anniversary edition" wiped out the jspm config files, not sure. should I go ahead and try to delete the |
@pocesar that sounds like it might fix the problem then. If you're able to clarify what state change exactly you think caused the issue that would be interesting to hear if there is anything we can do. |
@guybedford usually big windows updates messes with folder structure, file configurations, rename windows folder to windows.old, and so forth. symlinks also suffered, had some broken node_modules that were linked after the update, had to change my node_modules folder location. I don't think it's a problem with JSPM, although looked like it at first. maybe check if the file actually exists, and emit an error in case it doesn't, when doing something that will try to lookup the github token from the file (showing the actual config file path for easier of inspection, and not assuming |
@pocesar thanks for the update. |
Using jspm@beta, I'm having a problem (on Windows 10) when using jspm dl-loader
then I tried to see the current config
when I tried to do a
cat ~/.jspm/config
it obviously doesn't work in windows, although I manually created the .jspm folder inF:\Users\Paulo\.jspm
, it doesn't seem to be accessing the folder, nor creating any files. the folder permissions are fine. but I don't know where it's placing the config file.The text was updated successfully, but these errors were encountered: