New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wiredep #551
Comments
Send a PR to fix? |
I have investigated a bit, and have no clue about what is making bower.json not checking out. Both However, the other repo Leaflet.label just acts the same way. oO |
How just got it. The released tag doesn't include the bower.json file. Bower is checking out the last semver tag. EDIT: I can submit a PR to fix |
Needa get a proof this is fixed by the build process |
Assuming this is good now |
This commit duplicated
main
section of bower.json, and wiredep still doesn't work. In addition, the added "main" section is bad because it only contains the.js
file, while the older one contains also.css
(that wiredep can understand too)Overall, the thing that disallows wiredep to work was not the absence of
main
, but rather the fact that bower doesn't seem to checkout the file bower.json itself, probably due to a badignore
section (that I don't understand) inside bower.json. Wiredep, indeed, parses modules' bower.json to fetch main property, but when Ibower install leaflet.markercluster --save
, it doesn't checkout the file bower.json itself.Temporary solution, add this section in the root of your bower.json (your main module that need leaflet.markercluster) :
The text was updated successfully, but these errors were encountered: