Commit fc46dea
committed
Use npm install rather than npm ci
I _think_ the switch to npm ci is causing some issues with how a
babel/runtime dependency is being handled in MacOS vs Ubuntu. I'm
seeing build changes from this workflow that I can't reproduce in
my local environment at all: once with extensive gymnastics and
then never again.
I'm going to take the chance that `npm install` provides a way for
OS dependent versions to be installed in this massive web of crap
I don't want to understand.1 parent f12d40a commit fc46dea
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
44 | 44 | | |
45 | 45 | | |
46 | 46 | | |
47 | | - | |
| 47 | + | |
48 | 48 | | |
49 | 49 | | |
50 | 50 | | |
| |||
0 commit comments