Skip to content

Conversation

@toolmantim
Copy link

This updates parserlib to the latest version (0.2.3) which brings the new ✨, including fixes for missing properties (such as #366 / CSSLint/parser-lib#68)

Also passes ant test 👍

@nschonni
Copy link
Member

Parserlib is now pulled in through npm, so it will always use the latest from the 0.2.X releases

@stubbornella
Copy link
Member

Nick, do I need to do anything in particular?

On Thu, Aug 15, 2013 at 4:59 PM, Nick Schonning notifications@github.com
wrote:

Parserlib is now pulled in through npm, so it will always use the latest from the 0.2.X releases

Reply to this email directly or view it on GitHub:
#403 (comment)

@nschonni
Copy link
Member

@stubbornella no, I should just do a PR to remove the lib folder and the Ant stuff since it's not used/required anymore (and update the docs ...)

@toolmantim
Copy link
Author

@nschonni oh riiiight… I've only now noticed it's all been moved to npm & Grunt. Don't know how I missed that.

@toolmantim toolmantim closed this Aug 16, 2013
@nschonni
Copy link
Member

@toolmantim totally my fault for not cleaning up after Grunt landed 😦 That doesn't make contributing confusing at all 😄

@toolmantim
Copy link
Author

No problemo… just needs a few of these: 🚧 🚧 🚧 🚧

@nschonni
Copy link
Member

@toolmantim
Copy link
Author

@nschonni yep, sure does. One question though: why the need for the ant lint when there's already a grunt lint?

@nschonni
Copy link
Member

Because I missed it 😄 Fixed now.

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