Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed windows build behind proxy #62

Merged
merged 1 commit into from
Aug 17, 2014
Merged

Conversation

stustison
Copy link
Contributor

This update is to allow this grunt task to work behind a corporate proxy (using npm) and also allow it to run correctly on a Windows environment which it did not seem to do (I see someone else created an issue here that was similar #61 ). I've been using this for quite a while in our environment and it appears to work fine. I just thought I'd clean up the commits and do a pull request back to you guys so you could take advantage of this change.

@stefanjudis
Copy link
Contributor

You have to merge faster first, hmm?

But please please please. 😊 👍

@TechNickAI
Copy link
Collaborator

Can you fix the conflict?

@stustison
Copy link
Contributor Author

Yeah, I can fix the conflict. Just give me a while to make the change and test to ensure it still works. I'll post here again when it is good to go. ;)

Added casperjs to package.json so that npm could take care of downloading casper rather than doing it via the install.js script.
Removed install.js file since it wasn't needed. Modified casperjs script to simply look for casper in the correct location
Added npm install
Added npm preinstall
Added Node platform detection for casperjs to run on Windows
@stustison
Copy link
Contributor Author

Just ran a quick test and everything appears to be fine.

TechNickAI added a commit that referenced this pull request Aug 17, 2014
Fixed windows build behind proxy
@TechNickAI TechNickAI merged commit 625dc4d into ronaldlokers:master Aug 17, 2014
@TechNickAI
Copy link
Collaborator

Published as grunt-casperjs 2.0

@TechNickAI
Copy link
Collaborator

Should also fix #61

@TechNickAI
Copy link
Collaborator

Resolves #57

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants