Skip to content

Heroku: 'Is webpack still compiling?' #279

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

Closed
dino-koutrouzas opened this issue Apr 24, 2017 · 6 comments
Closed

Heroku: 'Is webpack still compiling?' #279

dino-koutrouzas opened this issue Apr 24, 2017 · 6 comments

Comments

@dino-koutrouzas
Copy link

Getting the following error ActionView::Template::Error (Can't find welcome/index.js in /app/public/packs/manifest.json. Is webpack still compiling?): on Heroku with this project: https://github.com/dino-k-29/rails-vue-webpacker

I'm using the following buildpacks:

1. heroku/nodejs
2. heroku/ruby
@gauravtiwari
Copy link
Member

@dino-k-29 Does that reference exist in manifest.json when you run bundle exec rails webpacker:compile locally?

@dino-koutrouzas
Copy link
Author

dino-koutrouzas commented Apr 24, 2017

@gauravtiwari yes, like so:

{
  "welcome/index.js": "http://localhost:8080/packs/welcome/index.js",
  "welcome/index.js.map": "http://localhost:8080/packs/welcome/index.js.map"
}

@gauravtiwari
Copy link
Member

@dino-k-29 Ah, so you have compiled assets locally and therefore, heroku assets:precompile hook doesn't get run.

-----> Preparing Rails asset pipeline
       Detected manifest.yml, assuming assets were compiled locally

More info here - https://devcenter.heroku.com/articles/rails-asset-pipeline#no-debug-output-at-all

Delete the assets folder and try again. If you rather compile it locally, please remove packs from .gitignore so both can be committed to source control.

@gauravtiwari
Copy link
Member

And the second problem is you are using es6 syntax, related to - #280

@gauravtiwari
Copy link
Member

es6 syntax issue should be fixed by #291

@gauravtiwari
Copy link
Member

Closing this one as the first one isn't an issue and the es6 problem is been tracked by #280

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants