All threads / Checking webpacker is cause of for time sink
Ask A Question


You’re not receiving notifications from this thread.

Checking webpacker is cause of for time sink

whaleGlider asked in Rails

Working on a ruby on rails application.

Let's say I make a small change to any class file and make a request to some page on my application. Then my response times are increased by anywhere from 20 seconds to 2-3 minutes or more. The next request I make takes less than a second.

This issue happens only on local machine(not in production) when caching is turned off i.e this happens whenever config.cache_classes = false in development.rb is set to false.

I found out that one highly possible culprit for this time sink or delay is webpacker. How can I check if webpacker is the culprit for this time sink using the terminal log. If not possible with the terminal log, what are steps I can take to confirm that webpacker is responsible for the time sink.

How to use Webpacker in alternate Rails contexts, such as engines or Docker ... open-source JavaScript projects, both for Node.js and browser runtimes.

Join the discussion

Want to stay up-to-date with Ruby on Rails?

Join 64,614+ developers who get early access to new tutorials, screencasts, articles, and more.

    We care about the protection of your data. Read our Privacy Policy.

    logo Created with Sketch.

    Screencast tutorials to help you learn Ruby on Rails, Javascript, Hotwire, Turbo, Stimulus.js, PostgreSQL, MySQL, Ubuntu, and more. Icons by Icons8

    © 2022 GoRails, LLC. All rights reserved.