Skip to content
This repository has been archived by the owner on May 30, 2023. It is now read-only.

Path is always null (because location.js is missing) #13532

Closed
RachelSatoyama opened this issue Aug 27, 2015 · 2 comments
Closed

Path is always null (because location.js is missing) #13532

RachelSatoyama opened this issue Aug 27, 2015 · 2 comments
Assignees
@JamesMGreene

Comments

@RachelSatoyama
Copy link

Just like in phantomjs, in phantomjs2 there's following line of code:
exports.path = path.resolve(__dirname, require('./location').location)

The thing is that location.js is not present in phantomjs2 package.
Thus, phantomjs2.path is always null.
@JamesMGreene
Copy link
Collaborator

Sounds like you might be using the phantomjs2 NPM module. Please file an issue with them at zeevl/phantomjs2 as this has nothing to do with Phantom core.

@JamesMGreene JamesMGreene self-assigned this Aug 28, 2015
@RachelSatoyama
Copy link
Author

My bad. I apologize for this. Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@JamesMGreene JamesMGreene

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JamesMGreene @RachelSatoyama