releasing now

1.5.5 is out with the fix

Hi Avo community! I've followed the installation guide, but when I visit

/avo

none of the resources are being served, it is completely unstyled. Is there something special I need to do to have those assets being managed and served by webpacker when in development mode?

hey there @User

I just pushed 1.6.0 to the demo app and it looks good

just for more context, Avo's asset pipeline is abstracted away. It does not interfere with you asset pipeline (awebpacker or sprockets)

I'd love to jump on a call with you to troubleshoot the issue

Hey All Started using Avo for some of my small sites after I saw it on the 2020 Ruby Advent calendar and love it. Found out today that upgrading to 1.0.0 or beyond will break any rails app that has the sprockets asset pipeline completely removed. Given the fact that Avo abstracted the asset pipeline completely I wasn't expecting any issues. From what I can see it's nothing to do with Avo itself, but a bug with stimulus-rails. Just thought you all might want to be aware of it. stimulus-rails has an open PR already to fix it.

hi there

do you have a link tot that stimulus-rails PR?

also, I'm not sure I understand. do you have a technical issue with avo at the moment?

we'd love to know about it and fix it

No issue with Avo itself, I just can't use anything beyond version 0.4.10 at the moment because of that stimulus-rails issue and thought you should all know about it in-case anyone else comes to you with a similar report.

got it

what can I do to test this bug with v1.0+? should I try to install it on a rail app without sprockets and without webpacker?

because it has been tested on apps with 1. only sprockets and 2. only webpacker

Strange that you all have tested it with just webpacker. My app has only webpacker, but I'm getting the assets issue "method_missing ': undefined method' assets' for Rails Application Configuration" every time I try and start my site with Avo 1.0.0 or beyond (or specificly hotwire-rails). If I manually apply the fix in that PR everything works fine.

hmm

this is weird

so I can definitely tell you it works with webpacker installed

https://avodemo.herokuapp.com/ is a webpacker app

I'm heading into a few calls now for about two-three hours, but really I'd like to solve this issue for you

can I contact you later to troubleshoot it?

I'm about to go to sleep. But I've got a minimal repo that I'm just getting up to Github that has the issue. Webpacker enabled and sprockets removed.

is the repo open-sourced?

Trying to run that gives me the "method_missing': undefined method `assets' for # (NoMethodError)" error

got it