From 95d8972a9ed84bb920adee45886de9a7daa513ce Mon Sep 17 00:00:00 2001 From: neeravarora Date: Tue, 15 Aug 2017 11:40:35 -0700 Subject: [PATCH] Updated getting-started.md by mentioning the steps needed to verify changes made to composer-playground package. (#1879) * Update getting-started.md * Update getting-started.md * Update getting-started.md --- contrib-notes/getting-started.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/contrib-notes/getting-started.md b/contrib-notes/getting-started.md index 1f2f53a122..4c63b0f5a4 100644 --- a/contrib-notes/getting-started.md +++ b/contrib-notes/getting-started.md @@ -79,6 +79,16 @@ You must bootstrap the repository so that all of the dependencies are installed You can then work with the packages under [packages/](packages/) on a per-package basis as any normal node.js package. +For example, inorder to run Playground UI locally you can run: + + $ npm start + +on composer-playground-api and composer-playground packages in turn followed by visiting: + + localhost:3000 + +from your browser. + Alternatively, you can execute npm commands across all of the packages at once using Lerna: