Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Commit 340d6d4

Browse files
authored
Merge pull request #6772 from karthik-ziffity/patch-4
Added grunt exec and watch commands once grunt is setup
2 parents 149953f + 280f35b commit 340d6d4

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

src/guides/v2.3/frontend-dev-guide/tools/using_grunt.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -77,6 +77,11 @@ Where the following notation is used:
7777
- `<language>`: specified in the `code_subtag` format, for example `en_US`. Only one locale can be specified here. To debug the theme with another locale, create one more theme declaration, having specified another value for `language`.
7878
- `<path_to_file>`: path to the root source file, relative to the `app/design/frontend/<Vendor>/<theme>/web` directory. You need to specify all [root source files of the theme]({{ page.baseurl }}/frontend-dev-guide/css-topics/css-preprocess.html#css_preprocess_terms). If your theme [inherits] from a certain theme, and does not contain its own root source files, specify the root source files of the parent theme.
7979
80+
Once these are set correctly, run grunt to watch your changes.
81+
82+
- Run `grunt exec:<theme>` from the root directory to republish the symlinks.
83+
- Run `grunt watch:<theme>`, so that grunt will watch for each and every changes you make.
84+
8085
## Using custom Grunt configuration files
8186
8287
There are several ways to declare a custom configuration file.

0 commit comments

Comments
 (0)