Closed albertmatyi closed 10 years ago
I think that once weak dependencies are properly implemented in the Meteor packaging system, we can add them in for both bootstrap-3
and bootstrap3-less
, etc. to ensure that the code for those packages is loaded first if bootbox is included. This should be available soon.
If the dependency is not added, there can be errors that show up during load.
Hi Tim,
Thanks for removing the bootstrap-3 dependency. Would you mind pushing latest to atmosphere, please? The version up there still has it in there so its getting pulled in for me whenever I do an mrt update
.
(Btw, we're still on bootstrap 2.)
@alanning you can't use the latest version of bootbox with bootstrap 2, anyway. All 4.x versions only work with bootstrap 3.
Thanks Andrew, I've pinned it to v3.2.2 in my app.
@alanning I think @TimHeckel pushed 4.2.1 to Atmosphere, but it's slightly misleading as it's just a commit from the master branch rather than any particular release. I think we should generally just follow the release schedule in the future so that version numbers correspond.
Hey. Do you know why atmosphere still reports version 4.2.0? And there is no way to update via mrt
. You can only use the release if you specify the specific branch/commit
http://atmospherejs.com/package/bootboxjs - still reports version 4.2.0 with bootstrap-3 as dependency
It was probably tagged but not released, due to Atmosphere being down when Tim tried to do it. I can fix this shortly - I'm probably going to remove the 4.2.1 tag as well.
For your convenience, I've tagged and published the version that Tim released as 4.2.1-master.1
since it was actually pulled from the bootboxjs git repo and not a versioned release. Since Meteorite is using semver now, it'll count as lower than the next possible release version which would be 4.2.1
(or 4.3.0
).
I don't know the proper solution, but the problem is that some people don't use the
bootstrap-3
dependency but thebootstrap3-less
, and we wouldn't want to include them both. And obviouslybootbox
would work with the latter as well.What I would like to propose is to remove the
bootstrap-3
dependency - as we don't have a mechanism to check if either one is already included and include it based on that information.Any opinions?