-
Notifications
You must be signed in to change notification settings - Fork 37
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
path.extname is deprecated. #115
Comments
|
same problem |
1 similar comment
same problem |
same here |
+1 |
same |
same here. |
I have the same problem here... 😢 |
So I was able to temporarily fix this issue... it could also just be a workaround so please follow this at your own risk. It did however remove the "deprecation" message from atom for me. On the deprecated call, click on the second path: In the these are lines 1318 and 1331 respectively.
I hope this helps. I was glad I no longer saw the deprecation message 😆 |
Created a Pull Request for this (#118) based on @AuggieMBP's comment |
Same problem... When an updated to the package will be released? I like much this package but don't like to have deprecation alert in my atom :( |
same problem |
same issue |
8 similar comments
same issue |
same issue |
same issue |
same issue |
same issue |
same issue |
same issue |
same issue |
Solution from @AuggieMBP solve problem |
same issue |
I have an issue the charset codification of the console, look this text: Thanks! |
Yup, same here.... |
FYI here is a Deprecated calls I am getting Argument to path.extname must be a string |
+1 |
3 similar comments
+1 |
+1 |
+1 |
@AuggieMBP Thanks man |
+1 |
o.O3 ---> |
+1 |
I have the same issue |
Still not fixed? |
still not fixed |
Argument to
path.extname
must be a stringThe text was updated successfully, but these errors were encountered: