Update README.md #1

Merged
merged 1 commit into from Feb 28, 2014

Conversation

Projects
None yet
3 participants
@james-gibson

Updated npm install instructions to match those on the npm site ( https://www.npmjs.org/package/crawler-hq )

Update README.md
Updated npm install instructions to match those on the npm site ( https://www.npmjs.org/package/crawler-hq )

randunel added a commit that referenced this pull request Feb 28, 2014

Merge pull request #1 from james-gibson/patch-1
Updated npm install instructions

@randunel randunel merged commit 8efaa96 into randunel:master Feb 28, 2014

@randunel

This comment has been minimized.

Show comment Hide comment
@randunel

randunel Feb 28, 2014

Owner

Thank you :)

Owner

randunel commented Feb 28, 2014

Thank you :)

@1602

This comment has been minimized.

Show comment Hide comment
@1602

1602 Feb 28, 2014

Collaborator

@james-gibson I'm just wondering, how you discovered this fork? Was it random or you run into the same issue (cookies), that was fixed in this fork?

Collaborator

1602 commented Feb 28, 2014

@james-gibson I'm just wondering, how you discovered this fork? Was it random or you run into the same issue (cookies), that was fixed in this fork?

@james-gibson james-gibson deleted the james-gibson:patch-1 branch Feb 28, 2014

@james-gibson

This comment has been minimized.

Show comment Hide comment
@james-gibson

james-gibson Feb 28, 2014

Actually far from random, I was attempting to install Crawler but it kept failing. I did some googling and found that this project was recently updated. Once I got Crawler-hq installed everything started working. I noticed the discrepancy while going through the readme.

Actually far from random, I was attempting to install Crawler but it kept failing. I did some googling and found that this project was recently updated. Once I got Crawler-hq installed everything started working. I noticed the discrepancy while going through the readme.

@1602

This comment has been minimized.

Show comment Hide comment
@1602

1602 Feb 28, 2014

Collaborator

@james-gibson thanks for sharing. this project is semi-private and we support it because we use it in production. unfortunately github doesn't provide decent way to identify what fork of abandoned project to use, their network graph is just half-way to solve this task, glad to know, that google makes it's job better than github.

Collaborator

1602 commented Feb 28, 2014

@james-gibson thanks for sharing. this project is semi-private and we support it because we use it in production. unfortunately github doesn't provide decent way to identify what fork of abandoned project to use, their network graph is just half-way to solve this task, glad to know, that google makes it's job better than github.

@james-gibson

This comment has been minimized.

Show comment Hide comment
@james-gibson

james-gibson Feb 28, 2014

Finding the npm page and seeing that the project was updated recently was all the info I needed to install it. I found my self in need of a web crawler for a programming easter egg hunt that I was tasked with. This worked great! (see https://github.com/james-gibson/simpleEnergy-web-crawler/blob/master/main.js )

Finding the npm page and seeing that the project was updated recently was all the info I needed to install it. I found my self in need of a web crawler for a programming easter egg hunt that I was tasked with. This worked great! (see https://github.com/james-gibson/simpleEnergy-web-crawler/blob/master/main.js )

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