Skip to content
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

Unable to run webpacker:install in a rails engine. #1124

Closed
etewiah opened this issue Dec 19, 2017 · 4 comments
Closed

Unable to run webpacker:install in a rails engine. #1124

etewiah opened this issue Dec 19, 2017 · 4 comments

Comments

@etewiah
Copy link

etewiah commented Dec 19, 2017

When I install the webpacker gem in a rails engine the "webpacker:install" command is not available. There is however a "app:webpacker:install" command available.

When I run it:

bundle exec rails app:webpacker:install

I get the following error:

rails aborted!
Don't know how to build task 'app:template' (see --tasks)
./bin/rails:13:in `require'
./bin/rails:13:in `<main>'
(See full trace by running task with --trace)

The only way to get the command to run is to cd into "spec/dummy" and run "webpacker:install". That installs webpacker into the "spec/dummy" directory though which is not ideal.

Just so I can learn more about webpacker I went ahead and installed it in the dummy app in my project here and it actually works but does not seem like the correct way to do things:

https://github.com/RealEstateWebTools/property_web_scraper

@gauravtiwari
Copy link
Member

@etewiah Thanks for filling the issue. Webpacker doesn't support engines yet, please see this thread for more details: #348

@etewiah
Copy link
Author

etewiah commented Dec 19, 2017

@gauravtiwari Thanks for the quick response. I did follow issue 348 and researched all mentions of webpacker and rails engines I could find.

While I could see that people were working on fixes for various tricky scenarios I did not see a clear statement that webpacker does not support engines at all. If that is the case then it would probably be good that this is mentioned explicitly in the main readme.

I'm actually getting some value out of having webpacker running in my dummy app so I'll carry on with that for now even though I know it is "wrong" :(

Hope we get some clarification soon about when support for engines might land.

@gauravtiwari
Copy link
Member

Lets track this in #1694

@zedtux
Copy link

zedtux commented Jun 1, 2019

I'm facing this exact error, @etewiah how did you fixed it?

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

3 participants