Windows/NTFS - Path to long about framework

[mantzas]

+1 trying to delete the folder was a pain. Maybe there was no consideration for us windows users (again)! I am refering to the package manager.

[EisenbergEffect]

This is related to how NodeJS handles packages and creates its directory structure. There's really nothing we can do about it. I would consider brining this issue up with the NodeJS/NPM teams.

[gep13]

We recently ran into the same problem with an un-related node project. We had to use the rimraf node module (https://github.com/isaacs/rimraf) to help with the deletion of the node_modules folder. We sometimes have to drill into the folder hierarchy and run rimraf a couple times, but you can get rid of the folders, eventually.

[Stoggy]

@EisenbergEffect Regardless if it's a NodeJS/NPM issue or not, it should be possible to finish the Get Started guide successfully, even for windows users.
As far as i can see, the current issue boils down to the package "conventional-changelog"
Maybe there's an alternative for this package?

[EisenbergEffect]

I'm not clear how working through the get-started tutorial involves deleting node packages. But regardless, this is not a bug in Aurelia or even the 3rd party gulp plugins. It's an issue with NodeJS on Windows and you will encounter it on various projects on Windows when trying to delete packages.

I'm open to alternatives for Windows users, in order to improve this, but I don't know of any at the moment. NodeJS is the de facto standard and really the only technology for doing this sort of work and Microsoft isn't building any alternatives...in fact they are embracing it with the next VS release. Maybe it's worth asking them to implement an advanced delete feature in VS?

[jwahyoung]

This is a bug with the Windows API, not an NPM bug. Windows support
260-char-length paths, maximum, regardless of the underlying file system.
It hasn't changed for years.

If you need to remove files, you might try working from Windows Powershell
and using short paths.

On Thu, Feb 5, 2015 at 7:56 AM, Rob Eisenberg [email protected]
wrote:

I'm not clear how working through the get-started tutorial involves
deleting node packages. But regardless, this is not a bug in Aurelia or
even the 3rd party gulp plugins. It's an issue with NodeJS on Windows and
you will encounter it on various projects on Windows when trying to delete
packages.

I'm open to alternatives for Windows users, in order to improve this, but
I don't know of any at the moment. NodeJS is the de facto standard and
really the only technology for doing this sort of work and Microsoft isn't
building any alternatives...in fact they are embracing it with the next VS
release. Maybe it's worth asking them to implement an advanced delete
feature in VS?

—
Reply to this email directly or view it on GitHub
#26 (comment).

[mantzas]

or you could shorten the length by copying a child higher up the hieracrchy in order to create shorter paths. that worked for me

[jdalton]

Just a heads up. lodash v3 has significantly reduced the dep graphs of its modularized packages:

[email protected]
├─┬ [email protected]
│ ├── [email protected]
│ └─┬ [email protected]
│   ├── [email protected]
│   ├── [email protected]
│   └── [email protected]
└─┬ [email protected]
  ├── [email protected]
  └── [email protected]

There's even a simplified form:

[email protected]
├── [email protected]
└─┬ [email protected]
  ├── [email protected]
  ├── [email protected]
  └── [email protected]