Question
Javascript error in precompiled asset: "Invalid or unexpected token" for code '#!/usr/bin/env node'
My site runs fine locally in development. However, deployed on digital ocean in the Ubuntu 16.04 environment, it breaks because the so-called ‘shebang’ line above, which is not in any of my original js code, nor directly in any of the js libraries I have incorporated into my project, errors in my browser console. The “#!/usr/bin/env node’ line is line #29589 in a precompiled asset.
My assets were precompiled locally an are included in my repo. I removed them all from my Production host and ran rake assets:precompile there, but still get the error. I manually removed the line from the precompiled file in question, restarted unicorn and nginx, yet still get the error, which I completely don’t understand.
This isn’t my code, but it’s somehow breaking my production site for unknown reasons, and I doubt it should be.
Can anyone explain to me:
- Is the line ’#!/usr/bin/env node’ supposed to be in my precompiled asset or not.
- If it is, why it breaks my production site, or, if it ain’t, why it’s there and how to make it not appear in my precompiled asset.
- what am I doing wrong in troubleshooting that manually deleting the offending line, then clearing my local cache and manually restarting unicorn and nginx on my droplet STILL results in the removed line appearing and breaking my site in my local broswer?
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.