Skip to content

Expected compile speed ? #55

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
defsdoor opened this issue Mar 30, 2021 · 8 comments
Closed

Expected compile speed ? #55

defsdoor opened this issue Mar 30, 2021 · 8 comments

Comments

@defsdoor
Copy link

I'm getting ~7 seconds to compile an unaltered pipeline - is this typical as it severely impacts my workflow ?

My PC has a AMD Ryzen 9 3950X CPU - it's not a slow machine :|

@dhh
Copy link
Member

dhh commented Mar 30, 2021

Is this using webpacker or the asset pipeline? If webpacker, it is what it is. We don't really have any control over that.

@defsdoor
Copy link
Author

Sorry - this is webpacker - do I have an option to not use webpacker yet when rolling with hotwire and stimulus (this is a brand new application I'm writing primarily to familiarise myself with these two) ?

@dmarcoux
Copy link

@defsdoor The short tutorial on https://hotwire.dev/ doesn't rely on webpacker, it's using the asset pipeline. This should get you started.

@leehericks
Copy link

Here’s how I start a new Hotwire app without webpacker.

rails new myapp --skip-javascripts

This skips webpacker, turbolinks and rails ujs.

Then add gem 'hotwire-rails' to your gemfile

bundle install
rails hotwire:install

This gives you a new rails app with a beautiful assets/javascripts folder with turbo and stimulus ready to go.

@defsdoor
Copy link
Author

@leehericks thanks for this - giving it a go now.

BTW - the option is --skip-javascript

@dmarcoux cheers

@leehericks
Copy link

@defsdoor Sorry, I swear I double checked that before posting 😅

@defsdoor
Copy link
Author

All seems to work ok - thank you all.

I'm really interested in tailwind - is anyone aware of a project or efforts to create a sass based version ? To me, using sass mixins is much more comfortable than postcss (and the beast it requires) rendering of the css.

I've already hit a need to add a minor customisation.
I guess I could do any customisations infrequently and generate a new tailwind.css outside of the development environment when needed.

@dhh
Copy link
Member

dhh commented Mar 31, 2021

Yes, if the app doesn't have webpacker, then it'll use the asset pipeline. --skip-javascript

@dhh dhh closed this as completed Mar 31, 2021
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

4 participants