This repository has been archived by the owner on Jul 24, 2019. It is now read-only.
fix issue with tryPhantomjsInLib on Elastic Beanstalk #590
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In v2.1.7,
tryPhantomjsInLib
wouldn't overwritelocation.js
if phantomjs was foundIn v2.1.8,
tryPhantomjsInLib
would overwritelocation.js
with an absolute location if phantomjs was foundThis breaks Elastic Beanstalk because they put your app in
/tmp/deployment
, runnpm install
andnpm rebuild
, then move your app to/var/app/current
.The
npm rebuild
was causinglocation.js
to have an absolute path as the location, which was no longer valid once the app was moved to/var/app/current
instead of/tmp/deployment
.The change I made should preserve some of the code cleanup by conditionally overwriting
location.js
iffindValidPhantomJsBinary
returns a valid path.Please bump the patch version after this is merged since it's a breaking change affecting all current Elastic Beanstalk deploys :)
Thanks for your work on this repo!