Closed iJackUA closed 1 week ago
This is connected issues https://github.com/rails/mission_control-jobs/issues/140
In our setup we are also useing esbuild
to compile JS. And sprockets-rails
to handle "assets:precompile".
I see that importmap-rails
are also in the Gemfile, but it is not being used by our app.
While I still believe there should be a real solution, like PRs mentioned above.
Solution for those who are trying to find a workaround and have the same pre-conditions like mine:
1) this solution assumes that you are using smth else, not importmaps in yout Rails app! and Importmap was just pregenerated by rails new
and never used, but also not removed.
2) remove gem "importmap-rails"
from Gemfile
3) remove config/importmap.rb
file
now mission_control does not overlap own importmap with your app's default importmap and works as expected!
Hey @iJackUA, this should have been fixed by #163. Do you mind verifying if things look good for you?
Going to close this one as it should be fixed now by #163.
After update 0.3.2 > 0.3.3 it started to fail when accessing UI pages (RAILS_ENV=development)
Rails app itself uses sprockets, so I suppose it is related to issue that caused 0.3.3 fix https://github.com/rails/mission_control-jobs/issues/169 my app is not api-only and had no issues with 0.3.2, but it failed to make
assets:precompile
in production env with 0.3.2still need to try, but maybe https://github.com/rails/mission_control-jobs/pull/163 is in the right direction (as in current error message it suggests manifest.js from parent app, but not from the mission_control engine, maybe it mixes them while precompiling?)
declaring it in "parent app"
manifest.js
liek suggested//= link controllers/application.js
does not help (and I believe it should not), not sure whyapplication-mcj
is being translated intocontrollers/application.js
path.