Closed phazor closed 5 months ago
Can confirm that this is indeed the case, having tried building with "phantomjs": "~1.9.2"
in package.json
which results in Phantom 1.9.19
being used. However, it appears that switching away from the specific Phantom version (1.9.2-6
) causes an issue with rendering certain Scratch-related assets within projects (perhaps in reference to this https://github.com/CodeClub/lesson_format/issues/87#issuecomment-60216405)
Considering this is EOL, I wouldn't expect a fix here.
I think that that node module (which has now moved here, but only installs phantomjs 2 now) just installs the phantomjs binary. You can still get 1.9.2 here: https://code.google.com/archive/p/phantomjs/downloads
I guess google code has just moved these download locations.
So I’d suggest just doing this bit manually, and removing the phantomjs
node module from the dependencies list.
Cheers @andylolz, that sounds like a sensible workaround.
We upgraded to 2.1.1 which worked: https://github.com/RaspberryPiFoundation/lesson_format/commit/7e4d1fd33df3dd83221a8dc2ae8aeeffd456880e
Whoa. Cool! Did it break loads of other stuff??
(NB the package is now called phantomjs-prebuilt
, so should probs update package.json accordingly)
@andylolz - just reviewing now the impact, will actually reopen this until we are certain cc @rik-cross
Thanks for chipping in!
Yeah... it didn't work, and I've reverted the version (https://github.com/RaspberryPiFoundation/lesson_format/commit/0f968e66cea8b5417b9e5d5383f6009107cb9f8e)
Does that mean this is still in use?
I stopped working on this when #168 happened.
@andylolz No, it doesn't seem to be in use unfortunately.
@andylolz - yeah everything in #168 is still true, but the project is still powering a couple of things. Very much due to be retired still.
Phantom 1.9.2 is no longer available. During a fresh npm install, phantomjs tries to retrieve a zip file from a location which is no longer correct *:
The fix is simple: allow patch versions, e.g.
~1.9.2
, in the package.json.This works fine for me locally (I'm building it on OSX). From this, I assume that pinning the version is no longer necessary, or there's a reason specific to another platform.