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

Added grunt exec and watch commands once grunt is setup #6772

Merged
merged 2 commits into from
Mar 3, 2020
Merged

Added grunt exec and watch commands once grunt is setup #6772

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1d114f9
Added grunt exec and watch commands once grunt is setup
karthik-ziffity Mar 3, 2020
280f35b
Small grammar update
dobooth Mar 3, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions src/guides/v2.3/frontend-dev-guide/tools/using_grunt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,11 @@ Where the following notation is used:
- `<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`.
- `<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.

Once these are set correctly, run grunt to watch your changes.

- Run `grunt exec:<theme>` from the root directory to republish the symlinks.
- Run `grunt watch:<theme>`, so that grunt will watch for each and every changes you make.

## Using custom Grunt configuration files

There are several ways to declare a custom configuration file.
Expand Down