|
wwb posted:No, but it seems that ala is down . . . They front-paged HN, seem to have recovered now though.
|
#
¿
Jan 30, 2014 20:17
|
|
|
|
| # ¿ May 4, 2024 07:18 |
|
|
Gul Banana posted:NTFS. You're right that *installing* packages has no issue -this is because npm uses relative paths. But I can't, say, scp the result around, or uninstall them, or work with them in many source control apps (even to gitignore them). Are people just.. living with this? My I present an actual back and forth between people on a github issue from 2014 about this: "FYI Node (and thus npm) always uses UNC paths internally, before actually calling into the filesystem. It is only third-party tools that have a problem. (Unfortunately one of those third-party tools is Windows Explorer, but, that's Microsoft's bug...)" "Claiming therefore, that Windows supports long paths ... is a(n) entirely disingenuous attempt to misrepresent the actual reality." "I don't really care about whatever word games you want to play around the word "support." Sure, if you wish, all I'm saying is that Node and npm are Windows compatible software that support long paths."
|
|
#
¿
Apr 9, 2015 06:24
|
|
|
Newf posted:Does there exist any tool that parses a page's source to produce a report on the dependencies being used? Wappalyzer for (at least) Chrome does this, though I'm not sure how good/accurate it is.
|
|
#
¿
Jun 12, 2015 18:19
|
|