Closed sebthom closed 4 years ago
Yeah, noticed it too. They've ditched nodejs@8 support, so you probably wanna bump it to v12.
Perhaps we should alter travix to install puppeteer@2 though, since currently none of the "new" features are super useful.
I have the same issue with nodejs 12, so I doubt this is the reason. Maybe some transitive dependency issues between puppeteer and http-server-legacy. I am testing with pinning the puppeteer version.
Odd. I was able to sidestep it like so: https://github.com/MVCoconut/coconut.ui/commit/d0f22b3395a9bfc0acec50ed2e34b55a47715901
I was wrong, the job was using node 11. I specified this in travis.yml:
dist: bionic
language: haxe
os:
- linux
I now install node 12 like this and it works:
install:
- |-
if [ "$HAXE_TARGET" == "js" ] && [ "$TRAVIS_OS_NAME" == "linux" ]; then
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/master/install.sh | bash && \
source $HOME/.nvm/nvm.sh && \
nvm install --lts && \
nvm use --lts
fi
Thanks for your reponses!
Since around three hours all my travis+haxe jobs are failing for the js target. It probably is related to the new pupeteer release that got published three hours ago and thus not travix's fault, but maybe you have an idea how to workaround this.