-
Notifications
You must be signed in to change notification settings - Fork 244
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
Better define what "dev" mode does and how it should work #1528
Comments
As said elsewhere. "dev" is super slow. In "prod" nothing gets regenerated. |
In dev it's super slow but the CSS gets regenerated. It's the JavaScript which isn't being regenerated, right? |
yes it is the JS. See PR #1526 |
Also bug #1525 is completely related. |
@hfiguiere To regenerate the JS when
Or
Tip for #878. |
Hi, this doesn't work for me. I think I'm stuck somewhere between older and newer version. When I run in "dev" mode, I have new javascript and CSS, when I switch to "prod" and delete /src/html/assets/cache/*, I have apparently old js, becouse lightbox stops appearing and upload doesn't work. :-/ I have also run the tbx-dot-js.sh with no effect. Is there a way, by which I can delete all old stuff and get new one to "prod" mode? |
@xvasek2 did you do these in order?
That should recreate the JS file. |
When setting
mode="dev"
the static assets (JS/CSS) should reflect the code that exist in the repository and not be pulled from a static asset cache.However, some of this has changed with #1219 and by adding
tbx.js
. This issue it to open a discussion about how to most easily work with the assets for a developer.The text was updated successfully, but these errors were encountered: