You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Just like #319 (which is supposedly fixed), I'm getting
ENAMETOOLONG: name too long
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.
The text was updated successfully, but these errors were encountered: