From 0eb3ce453fd9ae0465a37a9c8cf8d844f234f26e Mon Sep 17 00:00:00 2001 From: Robert Hurst Date: Thu, 12 Jul 2018 10:23:59 -0700 Subject: [PATCH] correction in CONTRIBUTING.md for PARCEL_WORKERS (#1715) Changed debugging recommendation for `PARCEL_WORKERS` from `PARCEL_WORKERS=0` to `PARCEL_WORKERS=1` as `PARCEL_WORKERS=1` will force parcel to use the local worker in the main thread exclusively. --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8152dd6e955..202fd5062a4 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -57,7 +57,7 @@ yarn test You can set `PARCEL_WORKERS` to the number of worker processes to spawn. -**NOTE:** `PARCEL_WORKERS=0` is handy for debugging, because all code will run on the main thread. You can then place breakpoints in Asset code. (Normally these breakpoints won't trigger, because the code executes in a subprocess.) +**NOTE:** `PARCEL_WORKERS=1` is handy for debugging, because all code will run on the main thread. You can then place breakpoints in Asset code. (Normally these breakpoints won't trigger, because the code executes in a subprocess.) **NOTE:** When developing plugins or new Asset types, run with `--no-cache` (or pass `cache: false` to `Bundler` options). Parcel uses caching by default, but during development you'll normally pass incomplete results into the cache. This can leave you wondering why you're constantly seeing old results.