Closed samal-rasmussen closed 3 years ago
@samal-rasmussen can you force push changes? I cannot see came CI error locally (build/linter/tests)
The original travis ci build errors were caused by node-sass, which is deprecated so I went ahead and changed over to the sass package and that seems to have worked for that issue.
But now the build is failing on optional catch bindings in the new versions of the dependencies. This was introduces in node 10 and the travis build is using 8 and 9. So this pr is stranded until someone updates the ci build.
@samal-rasmussen i've changed the versions to be LTSs. Still, you need to take latest (rebase) and push changes with updated .yml
, thx!
Oh that's how Travis works. Had I known it was that easy :)
Fix #305