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
Our tests run against src but not our build pipeline, which uses rollup. This leaves uncertainty when we update dependencies in our build chain.
Current Behavior
Travis only runs npm test currently, and tests run against our src (using babel)
Possible Solution
Adding the build script to travis would be a bare minimum to ensure that the build doesn't break.
Alternatively, we could run (or re-run) tests against the our build target(s). This would be more effort and possibly less friendly for local development.
Context
Maintenance becomes easier if we know dependency updates can be reliably accepted.
Your Environment
n/a
The text was updated successfully, but these errors were encountered:
Expected Behavior
Our tests run against
src
but not our build pipeline, which usesrollup
. This leaves uncertainty when we update dependencies in our build chain.Current Behavior
Travis only runs
npm test
currently, and tests run against oursrc
(using babel)Possible Solution
Context
Maintenance becomes easier if we know dependency updates can be reliably accepted.
Your Environment
n/a
The text was updated successfully, but these errors were encountered: