Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup tsc --watch workflow in examples and CLI project templates #922

Closed
3 tasks
bajtos opened this issue Jan 29, 2018 · 2 comments
Closed
3 tasks

Setup tsc --watch workflow in examples and CLI project templates #922

bajtos opened this issue Jan 29, 2018 · 2 comments
Labels
developer-experience Issues affecting ease of use and overall experience of LB users Examples

Comments

@bajtos
Copy link
Member

bajtos commented Jan 29, 2018

When I was working on the extension starter project, I added configuration allowing developers to avoid possibly long compilation time by leveraging tsc --watch mode. See DEVELOPING.md for the documentation.

We should apply this configuration to everything that can be used independently from our monorepo:

  • All example packages
  • CLI templates for app and extension projects

This is a follow-up task for #836.

Acceptance criteria

Update the following places in our monorepo

  • Example packages (replace this checkbox with an up-to-date list of example packages)
  • Extension project template
  • Application project template

For each place, make the following changes:

  • Setup build:watch and test:dev scripts in package.json (source)
  • Add .vscode configuration with "Watch and compile TypeScript" and "Test and lint" tasks - (source)
  • Add DEVELOPING.md file describing dev setup and workflow for developers using VS Code but also for developers using their own IDE/editor (source)
@bajtos bajtos added Examples developer-experience Issues affecting ease of use and overall experience of LB users Core-GA labels Jan 29, 2018
@dhmlau dhmlau removed the non-DP3 label Mar 27, 2018
@shimks
Copy link
Contributor

shimks commented Jul 26, 2018

@bajtos This feels like a duplicate of #1259. Could you please confirm?

@bajtos
Copy link
Member Author

bajtos commented Jul 30, 2018

Yes, this looks pretty much as a duplicate of #1259, which was implemented via #1336.

@bajtos bajtos closed this as completed Jul 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
developer-experience Issues affecting ease of use and overall experience of LB users Examples
Projects
None yet
Development

No branches or pull requests

3 participants