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
webpacker:compile
executes before or after assets:precompile
#169
Comments
@hone This is OK, because the |
@gauravtiwari we need to not error or warn when people are using the software correctly. Otherwise when 5.1 is released there will be dozens or hundreds of issues opened about the warning and it will be a bad experience for the end user. We also need to verify the current software is correct. |
@schneems I agree :) the warning is actually pointless now but perhaps, earlier it was needed. I think this will go away in stable 1.0 as there are some additions on way that will change the way this is handled. Perhaps someone from webpacker/rails core team can verify. |
I have commit to Rails. Terence posted because the behavior was unclear. I posted because it is still unclear. |
@schneems thanks for pointing this out. I think @gauravtiwari has acknowledged with agreement. Making it "go away" is a common goal. It's not the first time we tried addressing this warning. It was briefly mentioned at #116 too Moving forward, we can remove/replace that warning if it's no longer relevant (Is this true?) Anyone, please feel free to make suggestion so that a PR can be made to fix this. Just to add on, I tried deploying a new rails with |
@ytbryan No don't think this is relevant anymore and I will get rid of it in #153, with new manifest generation plugin. For heroku I think the vue option added sass loader, which needs node-sass, but I think that's installed on heroku. If you manually add node sass and add post install hook under scripts to rebuild node-sass, within your package.json I think it will deploy fine. Let me know if this works. |
Ohh the deployment works?did you tailed the logs - heroku logs -t to see why it's failing? |
Sorry, didn't had time to investigate just now. But seems this might be the fix http://stackoverflow.com/a/15693371/388280 (I might have missed it, can we set the port to fix Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch ?) I think node-sass is already included -> https://github.com/rails/webpacker/blob/master/lib/tasks/installers/vue.rake#L43 @gauravtiwari Do you have a working repo that you used to deploy to heroku on github?
|
Here's a bare bones example app I made https://github.com/schneems/rails51_webpacker We don't have yarn installed on Heroku yet for Ruby apps, you have to use @hone's brach or wait a day or two and use master. That being said, I would expect the deploy to fail instead of the server failing to boot. |
For clarity @hone and I work for Heroku. We are the Ruby buildpack maintainers. We want to make sure that webpacker and Rails 5.1 play nice on heroku. When I say "branch" I am referring to a branch of the buildpack that installs yarn heroku/heroku-buildpack-ruby#540. |
@ytbryan Ohh, you seem to binding to localhost. It should be Here is one, but using the latest feature branch - https://github.com/gauravtiwari/webpacker-demo-app |
Awesome, BTW we released support for Yarn https://devcenter.heroku.com/changelog-items/1114 Also that puma not booting problem is a bug in Rails. It's fixed on master but i documented a way around it in my changelog entry. |
That's awesome, no need of node build pack anymore. Great, actually I saw this behaviour a while ago but didn't realise it could be a bug. Thank you :) |
I think it still require buildpack https://devcenter.heroku.com/articles/ruby-support#installed-binaries Great, thanks Richard! |
@schneems Just noticed while deploying a webpacker app that, buildpack installs yarn, but doesn't run |
@gauravtiwari I used this app as a test. Does
|
@hone Nope, internally webpacker doesn't call |
@gauravtiwari I just tested a fresh Rails 5.1 app and |
The screenshot I posted before do not use any buildpack, just simple |
is that code available somewhere? |
Ahh right. Let me try again. |
👍 thanks for your help and testing this before RC1 lands ❤️ |
No worries @hone ❤️ This is the one I am deploying. Actually someone else had another issue whilst deploying to heroku, so this is a fork that fixes it - https://github.com/gauravtiwari/webpacker-erb-heroku. This is what I get - |
@gauravtiwari weird. i wonder if there's something in rails 5.1 that runs |
@hone Ohh yes, my bad I should have suspected that. It's definitely 5.1 - rails/rails@b1c08d8 |
@gauravtiwari 👍 mystery solved. That being said, it would be nice to probably make this work for |
@hone Ohh, that's too late. Alright, I won't pester you, talk later 👍 |
@hone I think it makes sense to add a standalone yarn installer for webpacker to make it compatible with other Rails version. Seems like that's the only missing piece. |
cool. so implement the rails equiv in webpacker itself?
…On 20/03/17 11:23, Gaurav Tiwari wrote:
@hone <https://github.com/hone> I think it makes sense to add a
standalone yarn installer for webpacker to make it compatible with other
Rails version. Seems like that's the only missing piece.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#169 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABASeZyGPNnxAx3lL5Q7MfzKD0rloD1ks5rnqf8gaJpZM4MaBLN>.
|
Yes, that's the plan. I can make a PR once #153 is merged. |
Hello, I'm working on getting webpacker supported on Heroku. I see this warning when running
rake assets:precompile
on an app.Is
webpacker:compile
meant to run after or beforeassets:precompile
? The code and comment suggest this isn't the case.The text was updated successfully, but these errors were encountered: