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
Description:
I propose the introduction of a feature that allows specifying certain directories to be monitored without triggering a full application rebuild. Instead, when changes are detected in these directories, a predefined command (e.g., npm build) would be executed.
Use Case:
In our current setup, we have a Node.js project nested within a Go project. The Node.js component is solely responsible for building JavaScript and CSS files. These files are then directly served by the Go application from the filesystem. Given this architecture, it's unnecessary for the entire application to undergo a rebuild whenever changes are made to the JS or CSS files. A more efficient approach would be to simply rebuild the JS and CSS assets.
The text was updated successfully, but these errors were encountered:
Description:
I propose the introduction of a feature that allows specifying certain directories to be monitored without triggering a full application rebuild. Instead, when changes are detected in these directories, a predefined command (e.g., npm build) would be executed.
Use Case:
In our current setup, we have a Node.js project nested within a Go project. The Node.js component is solely responsible for building JavaScript and CSS files. These files are then directly served by the Go application from the filesystem. Given this architecture, it's unnecessary for the entire application to undergo a rebuild whenever changes are made to the JS or CSS files. A more efficient approach would be to simply rebuild the JS and CSS assets.
The text was updated successfully, but these errors were encountered: