Change directory structure#2
Conversation
|
I'll explain this properly in the README. But the intention is that app/javascript is where all your app-like JS lives. Within that, we just use packs/ as a convention to create entry targets for webpack. So whatever you put in packs/ is what you want to have compiled via webpack as an entry. Every bit of "real code" should just live in app/javascript, like app/javascript/calendar/index.js or whatever. |
|
Thanks, I understand. Only one more thing, I think it would be better to use plural name like |
|
I went with But for this, we're building systems, not individual scripts. Kinda like if we did app/ruby rather than app/rubies. Hope that makes sense. |
|
OK, now I totally understand. Thanks a lot! |
…fest::MissingEntryError (#3232) * provides two more common errors (fix suggestions) for Webpacker::Manifest::MissingEntryError; see https://stackoverflow.com/questions/52639256/webpackermanifestmissingentryerror * puts back old veribalge for #4 (was #2) instead of * removing reference to npm
I think that
app/packs/javascriptsis closer to the Rails way of naming things, rather thanapp/javascript/packs/. Also,app/packs/javascriptsis more future-proof, as it will let us add other assets, for example stylesheets underapp/packs/stylesheets/.