New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong lookup path #196
Comments
Are you building assets for production? Typically, one would and browserify-rails wouldn't be trying to build the asset bundle in production. Something like this might be helpful: http://stackoverflow.com/questions/17767995/understating-how-assets-in-rails-4-work-in-production Other things to try are making sure modules are up to date -- so I'd look at |
I'm precompiling assets as a part of deployment process.
The command is ran from the app directory ( As you can see in the Ruby backtrace, browserify-rails is invoked. |
What happens if you run that same command in the root of your development environment? I think your deploy has funky path issues due to your versioning. Bit of a wild guess but would be good to rule out early. |
I can not reproduce this on my local machine (macOS) both with symlinked and real |
I think you're running into something like this capistrano/rails#51. I don't use Capistrano so I'm not sure how to fix it. |
Thanks for the link. I'll take a look a bit later. |
Hello,
I'm experience an issue in an app I didn't develop but I want to deploy.
My setup is Rails 5 app with broowserify-rails 4.1.0. I'm deploying the app with Capistrano.
It's a typical capistrano layout:
I'm getting an error like this:
Ruby backtrace
If you take a closer look at the module path it tries to find there seem to be one extra
..
. Without it I can find the file on disk.I searched on the web and can't find anything like this. I myself have no experience with either browserify. Please advice how to fix this issue. Please let me know if you need any additional information.
The text was updated successfully, but these errors were encountered: