You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In one of the TYPO3 we have there was no this part with TypoScript condition to clean the compressJs=0, concatenateCss=0 etc on development mode. On this TYPO3 instance on encore dev server mode the auto refresh (hot reload) of changes were not working and also developer needed to refresh page few times to have updated value of css/js. Additional issue was that the phpstorm core load was high after some work on project.
For some time I thought this behaviour is because of very big scss / js at this project and multi entry encore config.
But finally I found time to figure out that the reason is only concatenate being done by TYPO3 on dev server resources.
TYPO3 reads all external JS/CSS of local encore dev resources, made concatenate and instead of:
Additional drawback of this is that with time there are lot of such concatenate files (like GBs) and those files needs to be synced to docker and it slows down working experience (high core loads)
I am thinking now how many developers there are working like that with typo3_encore?
How many of them think this is how it should work.
Maybe we should update documentation at least or make some additional warning when concatenate is active on development mode? I am not sure.
What do you think?
The text was updated successfully, but these errors were encountered:
hi,
we have a base starter TYPO3 where by default we have:
In one of the TYPO3 we have there was no this part with TypoScript condition to clean the
compressJs=0, concatenateCss=0
etc on development mode. On this TYPO3 instance on encore dev server mode the auto refresh (hot reload) of changes were not working and also developer needed to refresh page few times to have updated value of css/js. Additional issue was that the phpstorm core load was high after some work on project.For some time I thought this behaviour is because of very big scss / js at this project and multi entry encore config.
But finally I found time to figure out that the reason is only concatenate being done by TYPO3 on dev server resources.
TYPO3 reads all external JS/CSS of local encore dev resources, made concatenate and instead of:
there is:
Additional drawback of this is that with time there are lot of such concatenate files (like GBs) and those files needs to be synced to docker and it slows down working experience (high core loads)
I am thinking now how many developers there are working like that with
typo3_encore
?How many of them think this is how it should work.
Maybe we should update documentation at least or make some additional warning when concatenate is active on development mode? I am not sure.
What do you think?
The text was updated successfully, but these errors were encountered: