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

ENAMETOOLONG: name too long upon install on Linux #492

Open
ramontayag opened this issue Sep 29, 2023 · 0 comments
Open

ENAMETOOLONG: name too long upon install on Linux #492

ramontayag opened this issue Sep 29, 2023 · 0 comments

Comments

@ramontayag
Copy link

Just like #319 (which is supposedly fixed), I'm getting ENAMETOOLONG: name too long

yarn add pipedrive --latest
yarn add v1.22.1
[1/5] Validating package.json...
[2/5] Resolving packages...
warning Resolution field "async@3.2.4" is incompatible with requested version "async@^2.1.1"
warning Resolution field "ejs@3.1.7" is incompatible with requested version "ejs@^2.6.1"
warning Resolution field "urijs@1.19.11" is incompatible with requested version "urijs@1.18.10"
warning Resolution field "async@3.2.4" is incompatible with requested version "async@~1.0.0"
warning pipedrive > superagent@7.1.6: Please downgrade to v7.1.5 if you need IE/ActiveXObject support OR upgrade to v8.0.0 as we no longer support IE and published an incorrect patch version (see https://github.com/visionmedia/superagent/issues/1731)
[3/5] Fetching packages...
error https://registry.yarnpkg.com/pipedrive/-/pipedrive-22.0.2.tgz: Extracting tar content of undefined failed, the file appears to be corrupt: "ENAMETOOLONG: name too long, open '/home/ramon/.cache/yarn/v6/npm-pipedrive-22.0.2-09285ee3b53d4674c6510e25c263477d22aecaf9-integrity/node_modules/pipedrive/dist/model/AnyOfRecentsActivityRecentsActivityTypeRecentsDealRecentsFileRecentsFilterRecentsNoteRecentsPersonRecentsOrganizationRecentsPipelineRecentsProductRecentsStageRecentsUser.js'"

I understand this might be related to the filesystem type. I'm on ext4. However, it's supposed to have been fixed yet the file is still there on master.

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

No branches or pull requests

1 participant