Create .npmignore save 2.5mb when publishing

[thanpolas]

No description provided.

[ryanseddon]

We don't publish to npm because of the nature of the project being a builder system.

[thanpolas]

but there are plans to publish, no?

[patrickkettner]

@ryanseddon - we are planning on it after 3.0

[patrickkettner]

We still need Gruntfile.js, as that is the most common use case for building modernizr. test would be required as a result of that. great catch on media, though!

[thanpolas]

no you don't

[patrickkettner]

yes, we do.

[ryanseddon]

Ah my bad.

[thanpolas]

Modernizr will be published on NPM with a singular purpose, to provide a build API to node applications.

Please explain why Gruntfile.js is required in the NPM Package and what are the expected use cases for it when distributed.

[stucox]

Please explain why Gruntfile.js is required in the NPM Package and what are the expected use cases for it when distributed.

Because Grunt is currently a dependency for building Modernizr. It’d be nice if it wasn’t, but at the moment it is.

[thanpolas]

oh... just saw that, sexy!

Removed Gruntfile.js and squashed

[stucox]

So we don’t need the test/ dir (to build)… but telling NPM to ignore this would mean it would grab a folder with a Gruntfile for which only some of the tasks actually worked. Is this a bit odd?

I agree that the point of publishing Modernizr to NPM would simply be to expose a build API though, so personally I’d be happy with this… @patrickkettner @ryanseddon ?

[patrickkettner]

sgtm

[ryanseddon]

yep all good

[stucox]

👍 cheers @thanpolas