collaborate

[jonschlinkert]

Hey @bahmutov! we seem to be working on similar things a lot.

I created this project: https://github.com/jonschlinkert/normalize-pkg to actually re-write properties in package.json to be more "idiomatic" (currently, I convert license to an object, which isn't technically correct, so I'm rethinking that one)

In any case, I was thinking we should link to each other's projects. I'll add a link to this on normalize-pkg. btw, you should consider moving the validation logic to a separate, generic node library, then require it back into the task. that way other libs can use it.

Also, if I recall you used grunt-readme at some point, so I wanted to mention that I created a new project you might like: Verb. It's essentially what grunt-readme was trying to do, but much better :-) thanks for this lib, feel free to close this.

[bahmutov]

Cool, I will def. add a link to normalize-pkg I like the idea, but I am using these two modules to validate and fix package.json - I am not doing much myself

• https://www.npmjs.org/package/fixpack
• https://www.npmjs.org/package/package-json-validator

My grunt-nice-package does not do much, but it just allows the user to pass a function to custom validate a property. One thing that I just added was require engines.node property (node 0.8 needs to be retired I think).

I used grunt-readme in several projects, really like it, especially when I have separate api examples, makes the entire readme assembly dead simple. So I will try Verb

On Fri, Mar 28, 2014 at 1:28 AM, Jon Schlinkert notifications@github.comwrote:

Hey @bahmutov https://github.com/bahmutov! we seem to be working on similar things a lot.

I created this project: https://github.com/jonschlinkert/normalize-pkg to actually re-write properties in package.json to be more "idiomatic" (currently, I convert license to an object, which isn't technically correct, so I'm rethinking that one)

In any case, I was thinking we should link to each other's projects. I'll add a link to this on normalize-pkg. btw, you should consider moving the validation logic to a separate, generic node library, then require it back into the task. that way other libs can use it.

Also, if I recall you used grunt-readme at some point, so I wanted to mention that I created a new project you might like: Verbhttps://github.com/assemble/verb. It's essentially what grunt-readme was trying to do, but much better :-) thanks for this lib, feel free to close this.

Reply to this email directly or view it on GitHubhttps://github.com/bahmutov/grunt-nice-package/issues/6 .

[bahmutov]

I could also run normalize-pkg as a step after / before fixpack runs to normalize package.json, if normalize-pkg allows using itself as a module

[jonschlinkert]

great!

if normalize-pkg allows using itself as a module

It does, I haven't documented the API yet, but it's a fairly small code base if you want to look around in the meantime

[bahmutov]

Added link to the README.md https://github.com/bahmutov/grunt-nice-package#related-projects