box / box-ui-elements

React Components for Box's Design System and Pluggable Components

Home Page:https://developer.box.com/docs/box-ui-elements

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

ENAMETOOLONG when attempting to install

michaelhays opened this issue · comments

Environment:

  • Elements version: 14.0.0

Desktop (please complete the following information):

  • OS: Linux

Steps to reproduce the problem:

pnpm add box-ui-elements

What is the expected behavior? (Screenshots can be helpful here)

Installs box-ui-elements correctly.

What went wrong? (Screenshots, console logs, or HAR files can be helpful here)

Packages: +1
+
 ENAMETOOLONG  ENAMETOOLONG: name too long, copyfile '/home/user/.pnpm-store/v3/files/ba/9a6e35378e8d6859ba72ec631d471026a46c209e65f541edd8e6954696b654ecf2e9dd4a26f237f984008ad9edeeaa3f137955974b24b3876d10177da09152' -> '/home/user/my-project/node_modules/.pnpm/box-ui-elements@14.0.0_16d78d4c5865b42183e731c766aacdba/node_modules/_tmp_66219_65d97d6eb7799a708d621fb8c1129bd9/src/components/avatar/__tests__/__image_snapshots__/avatar-stories-test-tsx-components-avatar-avatar-looks-visually-correct-when-using-story-components-avatar-with-url-fallback-to-initials-1-snap.png'
Progress: resolved 1395, reused 1366, downloaded 0, added 0

Additional context

This happened both on an existing project of mine, and on a new project. I had the same problem when trying to install with yarn.

The problem is that it tries to copy the __image_snapshots__, which have very long file names, such as avatar-stories-test-tsx-components-avatar-avatar-looks-visually-correct-when-using-story-components-avatar-large-1-snap.png. When nested in node_modules/, it exceeds the 256 character limit for the filesystem.

I think this could be fixed by removing the tests from the npm build of box-ui-elements.

I am surprised that I couldn't find anyone else who has run into this issue 🤔 I ran into the same problem on box-ui-elements versions 12, 13, and 15 (beta). Version 11 was able to install, though.

Does no one else have this issue? I've checked every month or so for over a year now, and the bug still persists :')