Include source files in bower "main"

[anush]

Since iframeResizer.contentWindow.min.js is a distributable file, it should be part of the bower package.

[davidjbradshaw]

OK that's interesting as the documentation doesn't say what the main field does and examples never have it as an array. This what gets downloaded when you install via bower.

└── [dave             238]  iframe-resizer
    ├── [dave             136]  js
    │   ├── [dave            6513]  iframeResizer.contentWindow.min.js
    │   └── [dave            5432]  iframeResizer.min.js
    └── [dave             204]  src
        ├── [dave           14987]  iframeResizer.contentWindow.js
        ├── [dave            9657]  iframeResizer.contentWindow.map
        ├── [dave           11768]  iframeResizer.js
        └── [dave            7311]  iframeResizer.map

Can you explain what this change does as I have to admit to being a bit confused by what the main is for.

[davidjbradshaw]

Ah found the answer to my question.

https://github.com/bower/bower.json-spec#main

Which say arrays are ok, but this should link to the versions in src rather than js.

[anush]

I've changed the bower "main" files to point to the source instead of the minified copy.

I've seen either used in other libraries, so though it was left up to the author's preference. Good to know there's a spec for it.

[anush]

I suppose it would be good to mention my primary reason for the pull request.

I use grunt-bower-task in my project so that I can manage my Bower dependencies via Grunt tasks. The grunt-bower-task uses what is defined in "main" to copy over the relevant files of the library.

Presently, in the case of iframe-resizer, only iframeResizer.min.js gets copied over. I needed the iframeResizer.contentWindow[.min].js file to also get recognized as a library file and get copied over. This PR solves this issue.

It makes perfect sense that the Bower spec indicates to include only the unprocessed copy (non-minified) as "main" files since the destination project may have it's own concatenation and minification process (as is true in my case).

[davidjbradshaw]

OK I will accept this. The one concern I had was that the two files where not designed to be included in the same built JS file. However, the bug I fixed last week for v2.5.1 should now prevent all the problems that might of caused.

[davidjbradshaw]

And thank you for the contribution.