linktyfon watch

storage Server-Side Command

alt_route Alias: tyfon w

Like tyfon serve, but also rebuilds SDK metadata on code change. As a result, it is a bit slower (and also less surgical on change detection).

1link$tyfon watch

#
# 🏗️ Building network layer code and client SDK metadata ...
#
#
# ✅ Network layer code and client SDK metadata built! 🍻
#
#
# 🚀 Serving exported functions on the netwrok ...
#
my-tyfon-server listening at http://localhost:8000

linkServe Options

Accepts all the parameters that tyfon serve accepts:

1link$tyfon watch --port 4000

2link$tyfon w -e ENV=staging

3link$tyfon watch --mode prod

linkClient Sync

Use --client or -c to specify a client project folder and watch will also keep the client SDK there in sync:

1link$tyfon watch --client ../my-tyfon-client

...
#
# 🚀 Serving exported functions on the netwrok ...
#
my-tyfon-server listening at http://localhost:8000
#
# Client SDK in sync with current API.
# client address /Users/Me/Projects/my-tyfon-client/
#

☝️ If, after a code change on the server, the API differs from what is installed on specified client folder, the watch command will also re-install the client SDK in that folder. Note that the SDK MUST be installed before hand with tyfon install.