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
Start grunt dev, then make a change to a file in core/js/libraries. Grunt will detect the change and start a build process, but the corresponding core/js/libraries file in the build folder will be unchanged.
In order to get the change into the build folder, you must manually stop then restart grunt dev.
Is this by design, or should libraries get updated on change like other files in src/?
The text was updated successfully, but these errors were encountered:
Subject of the issue/enhancement/features
Start
grunt dev
, then make a change to a file in core/js/libraries. Grunt will detect the change and start a build process, but the corresponding core/js/libraries file in the build folder will be unchanged.In order to get the change into the build folder, you must manually stop then restart
grunt dev
.Is this by design, or should libraries get updated on change like other files in src/?
The text was updated successfully, but these errors were encountered: