Skip to content

Commit e2444f6

Browse files
committed
Updates docs/yarn-scripts/overview.md
Auto commit by GitBook Editor
1 parent 7a1c316 commit e2444f6

File tree

2 files changed

+10
-9
lines changed

2 files changed

+10
-9
lines changed

docs/asset-pipeline/overview.md

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -15,14 +15,7 @@ The WP Emerge Theme comes with a powerful asset build process which covers a mul
1515
1. Run your desired build process:
1616
- To run the build process in production mode run `yarn build`
1717
- To run the build process in development mode run `yarn dev`. This will also watch files for changes and run Browsersync.
18-
19-
## Browsersync
20-
21-
By default, Browsersync will setup a simple web server and serve your files through a custom port in order to establish a communication channel between the build process and your browser like this:
22-
`http://localhost:3000/`
23-
24-
This is not ideal when working on WordPress projects that are setup in a subdirectory, for example. To let Browsersync know your site's url simply pass it as a parameter when running the dev task:
25-
`yarn dev --dev-url=http://localhost/my/nested/subdirectory/wordpress/`
18+
- For more information, check out the [Yarn Scripts](../yarn-scripts/overview.md) article.
2619

2720
## Importing assets
2821

docs/yarn-scripts/overview.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
## `yarn dev`
44

5-
Run the build process in development mode and enable Browsersync.
5+
Run the build process in development mode and enable [Browsersync](#browsersync).
66

77
## `yarn build`
88

@@ -15,3 +15,11 @@ Run the scripts and styles linters (`eslint` and `stylelint` respectively), repo
1515
## `yarn lint-fix`
1616

1717
Run the scripts and styles linters (`eslint` and `stylelint` respectively), fixing any fixable lint rule violations.
18+
19+
## Browsersync
20+
21+
By default, Browsersync will setup a simple web server and serve your files through a custom port in order to establish a communication channel between the build process and your browser like this:
22+
`http://localhost:3000/`
23+
24+
This is not ideal when working on WordPress projects that are setup in a subdirectory, for example. To let Browsersync know your site's url simply pass it as a parameter when running the dev task:
25+
`yarn dev --dev-url=http://localhost/my/nested/subdirectory/wordpress/`

0 commit comments

Comments
 (0)