From d4f159a3da0738aa045e9969dba2c6c13a7f6a8d Mon Sep 17 00:00:00 2001 From: Andrew Duthie Date: Thu, 19 Mar 2020 15:39:20 -0400 Subject: [PATCH] Docs: Include `npm run dev` guidance in "Getting Started" (#21015) --- docs/contributors/getting-started.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/contributors/getting-started.md b/docs/contributors/getting-started.md index 1a5656887b360..6236c404a71db 100644 --- a/docs/contributors/getting-started.md +++ b/docs/contributors/getting-started.md @@ -15,6 +15,8 @@ npm run build This will build Gutenberg, ready to be used as a WordPress plugin! +`npm run build` is intended for one-off compilations of the project. If you're planning to do continued development in the source files, using `npm run dev` will most often be the better option. This will configure the build to avoid minifying the generated output, rebuild files automatically as they are changed in your working directory, and configure dependencies as running in a development environment so that useful warnings and errors are logged to your browser's developer console. + If you don't have a local WordPress environment to load Gutenberg in, we can help get that up and running, too. ## Local Environment