Is this project still maintained? about grunt-casperjs HOT 8 CLOSED

@gorillamania
are bribes required to get #77 merged? :)

from grunt-casperjs.

Hey guys - I’ll merge stuff and push to npm over the weekend.

-Nick

On Jun 10, 2016, at 3:13 PM, Norbert de Langen [email protected] wrote:

@colinjoy https://github.com/colinjoy Do you need it quick? I've forked and merged #77 #77 here: https://github.com/ndelangen/grunt-casperjs https://github.com/ndelangen/grunt-casperjs
I've also merged #76 #76 and updated every dependency that was outdated.

It's published to npm here:
https://www.npmjs.com/package/@ndelangen/grunt-casperjs https://www.npmjs.com/package/@ndelangen/grunt-casperjs
It's published in my personal scope, because I'm still hopeful this project will come back to life, and I don't really want to create a competing package.

If like me you load grunt plugins using the npm package-name prefix, you might need to make a change for this to get picked up.

This is what I had to do:
ndelangen/sourcejs-Source@bd03251#diff-35b4a816e0441e6a375cd925af50752cL30 ndelangen/sourcejs-Source@bd03251#diff-35b4a816e0441e6a375cd925af50752cL30
I've run tests that came with the project, and I've tested the published version inside a project on my machine. I'd like your feedback.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #72 (comment), or mute the thread https://github.com/notifications/unsubscribe/AAItdFZ3crb8n9hnzKAEBbX6ZtynWQnyks5qKeGQgaJpZM4FhUZL.

from grunt-casperjs.

I've got access to the repo and npm repository, so I'll push buttons if others do the work. :)

from grunt-casperjs.

Excellent thank you @gorillamania :)

from grunt-casperjs.

@colinjoy Do you need it quick? I've forked and merged #77 here: https://github.com/ndelangen/grunt-casperjs

I've also merged #76 and updated every dependency that was outdated.

It's published to npm here:
https://www.npmjs.com/package/@ndelangen/grunt-casperjs

It's published in my personal scope, because I'm still hopeful this project will come back to life, and I don't really want to create a competing package.

If like me you load grunt plugins using the npm package-name prefix, you might need to make a change for this to get picked up.

This is what I had to do:
ndelangen/sourcejs-Source@bd03251#diff-35b4a816e0441e6a375cd925af50752cL30

I've run tests that came with the project, and I've tested the published version inside a project on my machine. I'd like your feedback.

from grunt-casperjs.

I can create a single PR for you updating everything, if you'd like?

I kinda already had, then pushed to many things to it by mistake, so closed it.

Let me know if that's something you'd want. Cheers, thanks for your time!

from grunt-casperjs.

Anything you can do to make it easier would be great.

-Nick

On Jun 10, 2016, at 3:17 PM, Norbert de Langen [email protected] wrote:

I can create a single PR for you updating everything, if you'd like?

I kinda already had, then pushed to many things to it by mistake, so closed it.

Let me know if that's something you'd want. Cheers, thanks for your time!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #72 (comment), or mute the thread https://github.com/notifications/unsubscribe/AAItdKG1rq4vHR1T-K3Ct0ZAOWCQQJBNks5qKeKUgaJpZM4FhUZL.

from grunt-casperjs.

#79

from grunt-casperjs.