Digests lookup fails due to invalid path construction about webpacker

[widescape]

I can confirm that #97 resolves the issue.

I'm in team with @serioushaircut and was seeing the same issue. @gauravtiwari

[serioushaircut]

Found the very same problem today. That's the way Rails.root.join works with an absolute path in the middle.

irb(main):004:0> Rails.root.join('public', '/lib')
=> #<Pathname:/lib>

So the fallback in case no config available for these paths entails an absolute path '/packs' for digests_path which might break your setup depending on your permissions.

Simple workaround (not fix) is to configure packs_dist_path in your production/staging environment to be 'packs' hence overriding default '/packs'.

The path assembly based on packs_path, digest_path, etc. can be found in at least two places:
lib/tasks/webpacker.rake
lib/webpacker/railtie.rb

[gauravtiwari]

@serioushaircut Hey, yes i tried that but it breaks the asset path because the same packs_dist_path is used for constructing asset path in the view.

ActionView::Template::Error (The asset "packs/home-react-component-5939abb942a18ece63be.js" is not present in the asset pipeline.):

[serioushaircut]

@gauravtiwari mmh we could deploy without any errors after setting the relative packs path. I'm gonna check why is that.

[gauravtiwari]

@serioushaircut Yeah, the app deploys fine, but there is a runtime error.

[serioushaircut]

@gauravtiwari apparently, I did not read your issue carefully. You are right. We get a runtime error on the staging system, which I attributed to another failing part. Still digging what's going on during deployment on heroku.

[gauravtiwari]

@serioushaircut Yeah, right did you take a look at this PR #97 ?

[gauravtiwari]

Cool @widescape 👍 Yeah, not sure if it's the best solution, but it fixes the issue.