Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Path too long issues on Windows

See original GitHub issue

I am having problems on Windows when creating installers for our application. We have set asar = false for our builds but now we are getting Path too long errors. I have taken a look at the Electron App Packaging docs and they suggest that you can use a combination of app.asar and app.asar.unpacked.

The problem lies within our node_modules directory. I have files within my source that need to be unpacked but would like to have node_modules in an asar archive to avoid these errors. When I attempt to do this though my app is unable to find any modules.

Is my understanding of this method correct or am I just missing some steps here?

Issue Analytics

State:
Created 7 years ago
Comments:10 (4 by maintainers)

Top GitHub Comments

2reactions

whench18commented, Apr 16, 2017

hi there… if there is any issue about path too long I can suggest one best solution. try the Long Path Tool and it will make your life easier. thanks.

0reactions

surajpindoriacommented, Sep 29, 2016

I have tried this and can’t seem to get it working. On Mac I am only able to require specific files using its path relative to the .asar (require('app.asar/node_modules/index.js')), not the whole module itself. Windows I can’t do either.

Is this the intended behavior?