You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 4, 2023. It is now read-only.
You should be able to provide multiple config paths to the serve command and run the fakes at once.
Right now, if you have multiple ncdc config files, you have to run the serve command many times. The resource drain can be especially bad when using watch mode, because you could have the typescript compiler running 5 (or as many config files you have) times in the background.
I think this will get done as part of the programmatic API/config file thing. But here's an intermediary solution:
Change the command to be like: ncdc serve ./path/to/config1.yml ./path/to/config2.yml 4000 -c mytsconfig.json
Outcome:
./path/to/config1.yml will be served on port 4000
./path/to/config2.yml will be served on port 4001
The typescript compiler will only need to be invoked once, using the single specified tsconfig.json
Because this is only an intermediary change, I think auto increment of the port is good enough.
The text was updated successfully, but these errors were encountered:
Summary
You should be able to provide multiple config paths to the serve command and run the fakes at once.
Right now, if you have multiple ncdc config files, you have to run the serve command many times. The resource drain can be especially bad when using watch mode, because you could have the typescript compiler running 5 (or as many config files you have) times in the background.
I think this will get done as part of the programmatic API/config file thing. But here's an intermediary solution:
Change the command to be like:
ncdc serve ./path/to/config1.yml ./path/to/config2.yml 4000 -c mytsconfig.json
Outcome:
Because this is only an intermediary change, I think auto increment of the port is good enough.
The text was updated successfully, but these errors were encountered: