4 ms·

Hope for fixes for stuff like npm, too.

• orf 9y ago
  Fixes for what, specifically?
  • komali2 9y ago
    Perhaps they only used it at the very beginning, when network requests were horribly broken, to the point that you couldn't even do an npm install. I haven't had any issues lately with NPM however. Don't want to speak for them though so let's see
  • godmodus 9y ago
    Npm is broken for example, it's apath exception when it looks into the os api. It expects linux defaults. The npm guys are trying to f8x it last i saw. Shame the module causes that. Itll trinkle down to many other Tools.
    • zadjii 9y ago
      Is this windows npm, or linux npm running on WSL? Because I believe that linux npm works just fine...
      • apardoe-MSFT 9y ago
        I've used Linux npm on Ubuntu/WSL without any issues.
  • mcdirty 9y ago
    I initially had problems with max character length for paths. When npm installed dependencies really deep down, Windows became unable to move or delete such files. I think it's been fixed with Yarn's flat dependency structure, which I think npm has also gone or is going to in the near future.
    • moogly 9y ago
      That change was made in NPM3, before Yarn was publicly released.
    • zadjii 9y ago
      Wait, is that for the Windows npm or the linux npm running on WSL? I don't believe the second would have ever had that problem