Skip to content
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

Windows x64 Installation Problem w/ Path Names #866

Open
GaryFurash opened this issue Nov 9, 2017 · 14 comments
Open

Windows x64 Installation Problem w/ Path Names #866

GaryFurash opened this issue Nov 9, 2017 · 14 comments
Labels

Comments

@GaryFurash
Copy link

Even when trying to extract to the root directory (e.g., C:\Laverna) generates the message "Destination Path Too Long" (node-modules

@wyldphyre
Copy link

I can confirm this on a 64 bit Windows 10 installation.

@brodiefairhall
Copy link

Same issue on Win 10 64 bit

@brodiefairhall
Copy link

Same issue with the 32bit zip for 7.51 and 7.5
Tried to Unzip on a linux machine and it failed as well

@S-ed
Copy link

S-ed commented Nov 17, 2017

No wonder here...
screenshot 1510924458

@wyldphyre
Copy link

I'd heard that Node was bad at dependancy management, but jeez.

@S-ed
Copy link

S-ed commented Nov 17, 2017

@wyldphyre *npm But yeah. I've even thought about writing a paper how to improve it some time ago. But was afraid all the efforts will be wasted and shelved this idea until better times.

@EggPenguini
Copy link

Expanded zip to C:\L\ Same problem, path too long. Win10, 64 bit.

@JimmyRascon
Copy link

I have solved it by unzipping to C:\L\ and omitting the errors. Then I used this workaround to flat the node_modules folder tree in C:\L\resources\app.
https://scottaddie.com/2015/08/16/npm-vs-windows-max_path-limitation/
After that I renamed and moved the "L" folder wherever I want. It's ugly but it works.

@S-ed
Copy link

S-ed commented Dec 20, 2017

@JimmyRascon The problem of this solution is "omitted" files are not there anymore.
Even if you use some third party app (like Total Commander) that could bypass OS limitation of path length (256 characters), OS won't be able to access them.

Probably, node still will be, but not sure.

@JimmyRascon
Copy link

@S-ed You are right, the omitted files are not there, they are node dependencies and some of them are duplicated. Using the "flatten-packages" command gets the most updated version of every package, in my case it's working but I'm not 100% sure it will not produce any obscure bug.
Here is my Laverna folder in case it is useful for someone.
https://www.dropbox.com/s/xyqviv8sybd3laf/laverna-0.7.51-win32-x64-mod.zip?dl=0

@wwebfor wwebfor added the bug label Dec 25, 2017
@ansib
Copy link

ansib commented Feb 12, 2018

Upgrade to a newer node.js and also the npm version would fix this path problem. (Version 6 is LTS).

@ParkerD13
Copy link

Got the same problem. Almost all updates are from a year ago. The webapp.zip download is broken. I hope Laverna is still alive.

@funilrys
Copy link
Contributor

Hi there,

Unfortunately this issue will never be fixed here.

Please report to #971 (comment) for the current state of this project and https://github.com/encryptic-team/encryptic for the future of this project.

Have a nice day/night.

Cheers,
Nissar

@daed
Copy link

daed commented Oct 13, 2018

I saw that. I've been able to skip those files and still run Laverna.

I just want to point out that Encryptic (and my pre-Encryptic Laverna release) don't appear to have those issues, though there's a handful of regressions in features that I'm working on that might be an issue otherwise depending on your use case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests