Skip to content
This repository has been archived by the owner on Apr 9, 2021. It is now read-only.

Dev dashboard + watcher #10

Open
wokalski opened this issue Sep 7, 2019 · 2 comments · May be fixed by #17
Open

Dev dashboard + watcher #10

wokalski opened this issue Sep 7, 2019 · 2 comments · May be fixed by #17
Assignees

Comments

@wokalski
Copy link
Collaborator

wokalski commented Sep 7, 2019

Currently the development process is extremely tedious. We need multiple commands and since we don't run tsc in the watch mode, it's extremely slow. I'd like to create a dashboard based built with ink which will watch and build all packages and run the server's from one interface.

Dashboard

The user should be able to simply run yarn start-dev in the root package and they should see the dashboard. It should automatically launch all build tools and servers and relaunch them if needed. It should essentially do what yarn build in the root does + yarn start in examples/server + yarn start in examples/client all in the watch mode. I would like to avoid running watch mode directly but tsc is too slow so we cannot avoid that.

@czystyl czystyl self-assigned this Sep 9, 2019
@czystyl
Copy link
Collaborator

czystyl commented Sep 9, 2019

I'll take care of it.

@wokalski
Copy link
Collaborator Author

wokalski commented Sep 13, 2019

We are going to run the following:
Servers:

  1. React Native Bundler
  2. Nars server (bundled with parcel, maybe in some watch mode?)
    Build processes:
  3. tsc in packages/nars
  4. tsc in packages/nars-client
  5. tsc in packages/nars-common
  6. generate_schema in packages/nars-common
  7. Bucklescript in packages/nars
  8. Copying to dist in packages/nars (although feel free to remove this step if you have a better idea)

I think that's sufficient. It'd be great to run tsc in --watch because it's very slow to start. That said if it turns out problematic don't bother to run it in watch. We can improve it later.

@czystyl czystyl linked a pull request Sep 14, 2019 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants