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

Split npm start into an init and watch script #742

Merged
merged 1 commit into from
Sep 25, 2018
Merged

Conversation

turt2live
Copy link
Member

This is to better support riot-web's build process without losing the functionality supplied by npm start. The watch script no longer performs an initial build and thus start:init has been created for this purpose.

Required for element-hq/element-web#7355

This is to better support riot-web's build process without losing the functionality supplied by `npm start`. The watch script no longer performs an initial build and thus `start:init` has been created for this purpose.
@ara4n
Copy link
Member

ara4n commented Sep 25, 2018

lgtm

@ara4n ara4n merged commit 3e32f47 into develop Sep 25, 2018
@turt2live turt2live deleted the travis/build-process branch September 25, 2018 16:32
turt2live added a commit to element-hq/element-web that referenced this pull request Sep 25, 2018
With the react-sdk and js-sdk having their `npm start`s split out (as per matrix-org/matrix-react-sdk#2175 and matrix-org/matrix-js-sdk#742) we can trigger an initial build ourselves and start the watcher afterwards. This canary approach has a very slight speed increase over serially running all the commands as the watcher can be started as early as possible.

This all can be improved and potentially eliminated with a bit more planning, however: #7386
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants