You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've a setup, where my bower dependencies get included automatically via wiredep and I merge them afterwards with useref.
This works fine for all dependencies, but masonry. I've tried moving masonry to the beginning as well as the end of those dependencies, but I'm always getting the same error. When I take out masonry and add an extra reference to your cdn link, it works. (Also all the other scripts work).
I've seen this issue: #618 and discovered that masonry's bower file is linking the wrong main file (#725) but even if I overwrote the main file to the correct one, I was still getting the same error. The cdn-file and bower files are identical, so probably the problem is somewhere in how wiredep is merging the files together?
Before that, I was already using masonry bundled together with ASP.Net and that worked fine. Any ideas what could be wrong here?
The text was updated successfully, but these errors were encountered:
desandro
changed the title
TypeError: Cannot read property Item of undefined when using masonry with bower
Wiredep TypeError: Cannot read property Item of undefined when using masonry with bower
Jul 22, 2015
I've a setup, where my bower dependencies get included automatically via wiredep and I merge them afterwards with useref.
This works fine for all dependencies, but masonry. I've tried moving masonry to the beginning as well as the end of those dependencies, but I'm always getting the same error. When I take out masonry and add an extra reference to your cdn link, it works. (Also all the other scripts work).
I've seen this issue: #618 and discovered that masonry's bower file is linking the wrong main file (#725) but even if I overwrote the main file to the correct one, I was still getting the same error. The cdn-file and bower files are identical, so probably the problem is somewhere in how wiredep is merging the files together?
Before that, I was already using masonry bundled together with ASP.Net and that worked fine. Any ideas what could be wrong here?
The text was updated successfully, but these errors were encountered: