![]() ![]() node_modules/) to cut the file path down before trying to delete it again. node_modules/a/node_modules/b/node_modules/c/./node_modules/h/) in Windows Explorer and move it somewhere closer to the root (e.g. Most people have probably been lucky enough to only have come across this problem when trying to delete dependencies where then Windows complains that the path is too long.Ī simple way around this is to take a module halfway down deep into your dependency graph (i.e. It's nice but in hindsight it's obviously incompatible with Windows's path length limit. your-project/node_modules/a/node_modules/b/) and so on recursively. If those dependencies have dependencies of their own they're stored in their own node_modules directory (i.e. Npm stores your dependencies (listed in your package.json) in a node_modules directory. Windows users know that they get left out in the cold often by npm package maintainers but even the design of npm itself is a problem on Windows from the get-go. Neither this problem nor our solution are exclusive to Node.js but a lot of the victims of the path length problem were probably running Node.js on Windows. Even if you haven't, feel free to take pleasure from reading my horror story. There's no real workaround but there are preventive measures you can take. You could've ran into this problem locally or on end users' machines. You might have been unfortunate enough to learn that Windows has a 256 character limit on file paths. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |