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 Nov 2, 2019. It is now read-only.
Trying to solve #125 & #119 has made me realize that our dependencies are kind of a mess right now. Keeping track of which versions we're using, making sure they load in the correct order, and request-bombardment are all becoming issues. Using Browserify is a smart move in the long run and it will make our code a lot more reusable and our dependencies centrally managed. I also think it will directly fix the flaky behavior that we're seeing in #119.
That said, we would need to modify the deploy script to invoke browserify in some way. I'm not totally sure what is available to us from CircleCI; it looks like we're auto-provisioning turbolift to execute the deploy right now. Can we execute npm scripts from CircleCI? @AbhiAgarwal
The text was updated successfully, but these errors were encountered:
Trying to solve #125 & #119 has made me realize that our dependencies are kind of a mess right now. Keeping track of which versions we're using, making sure they load in the correct order, and request-bombardment are all becoming issues. Using Browserify is a smart move in the long run and it will make our code a lot more reusable and our dependencies centrally managed. I also think it will directly fix the flaky behavior that we're seeing in #119.
That said, we would need to modify the deploy script to invoke browserify in some way. I'm not totally sure what is available to us from CircleCI; it looks like we're auto-provisioning turbolift to execute the deploy right now. Can we execute npm scripts from CircleCI? @AbhiAgarwal
The text was updated successfully, but these errors were encountered: