3 ms·

> npm: Upgrade to npm 2.14.7 from 2.14.4, see release notes for full details (Kat Marchán) #3299 Is that correct that npm 3.x with the flat node_modules isn't

> npm: Upgrade to npm 2.14.7 from 2.14.4, see release notes for full details (Kat Marchán) #3299 Is that correct that npm 3.x with the flat node_modules isn't in the first lts tree? We're still very likely to run into path length problems on Windows? That would be a shame. I know 3.x doesn't fix it but anything to make it less likely is a win. Now we're screwed for nearly 3 years.

tbrock 11y ago
I'm not a node or npm apologist but it is seriously time Microsoft update what it considers a reasonable maximum PATH length for Windows to something that makes sense for this era of computing (as well as the tiny ass box you type it into) We are on a roll with resizable terminals that reflow text in Windows 10 though so I won't push my luck.
- WorldMaker 11y ago
  It's not really a simple change: this is Microsoft respecting decades of API backward compatibility. New APIs support much higher PATH length, for what it is worth, it's just that a lot of software, for various accumulated reasons, rely on older APIs. For whatever their other faults, it's hard to blame Microsoft for treating backwards compatibility seriously. It's an amazing thing that in 2015 you can still run VB4-built Win32 application binaries built in 1995. (Not that I recommend people actually do so, given a choice in the matter, of course.)
  - jimmcslim 11y ago
    Agreed. But it still a bit disappointing that they haven't improved the GUI for editing the system path (as observed by the parent comment), but perhaps that also impacts backwards compatibility in some subtle way.
    - WorldMaker 11y ago
      The GUI has gotten a refresh in recent Windows 10 builds: http://www.ghacks.net/2015/09/22/microsoft-improves-environment-variables-editor-in-latest-windows-10-build/ http://www.ghacks.net/2015/09/22/microsoft-improves-environm...
- Bjartr 11y ago
  Take a look at "rapid environment editor". It solves the " tiny ass box" problem.
- Bjartr 11y ago
  Take a look at "rapid environment editor". It solves the " tiny ass box" problem.
jyunderwood 11y ago
I don't think that means "we're screwed." Perhaps npm can now use this LTS as a baseline for v3, since you can upgrade npm separately from Node.
ihsw 11y ago
There are still path length issues on Windows, yes. Here is a stop-gap: https://www.npmjs.com/package/flatten-packages https://www.npmjs.com/package/flatten-packages
- Already__Taken 11y ago
  An LTS release is a really nice time to wrap up all these "and then" steps to getting software working. Especially if you want software deployed across an organisation.

tbrock 11y ago

I'm not a node or npm apologist but it is seriously time Microsoft update what it considers a reasonable maximum PATH length for Windows to something that makes sense for this era of computing (as well as the tiny ass box you type it into) We are on a roll with resizable terminals that reflow text in Windows 10 though so I won't push my luck.

WorldMaker 11y ago
It's not really a simple change: this is Microsoft respecting decades of API backward compatibility. New APIs support much higher PATH length, for what it is worth, it's just that a lot of software, for various accumulated reasons, rely on older APIs. For whatever their other faults, it's hard to blame Microsoft for treating backwards compatibility seriously. It's an amazing thing that in 2015 you can still run VB4-built Win32 application binaries built in 1995. (Not that I recommend people actually do so, given a choice in the matter, of course.)
- jimmcslim 11y ago
  Agreed. But it still a bit disappointing that they haven't improved the GUI for editing the system path (as observed by the parent comment), but perhaps that also impacts backwards compatibility in some subtle way.
  - WorldMaker 11y ago
    The GUI has gotten a refresh in recent Windows 10 builds: http://www.ghacks.net/2015/09/22/microsoft-improves-environment-variables-editor-in-latest-windows-10-build/ http://www.ghacks.net/2015/09/22/microsoft-improves-environm...
Bjartr 11y ago
Take a look at "rapid environment editor". It solves the " tiny ass box" problem.
Bjartr 11y ago
Take a look at "rapid environment editor". It solves the " tiny ass box" problem.

jyunderwood 11y ago

I don't think that means "we're screwed." Perhaps npm can now use this LTS as a baseline for v3, since you can upgrade npm separately from Node.

ihsw 11y ago

There are still path length issues on Windows, yes. Here is a stop-gap: https://www.npmjs.com/package/flatten-packages https://www.npmjs.com/package/flatten-packages

Already__Taken 11y ago
An LTS release is a really nice time to wrap up all these "and then" steps to getting software working. Especially if you want software deployed across an organisation.