These are chat archives for ractivejs/ractive

14th
Aug 2017
Joseph
@fskreuz
Aug 14 2017 19:51
Any thoughts on packaging every plugin with ractive (as opposed to separate repos/packages), as well as the approach to monorepo? https://github.com/ractivejs/ractive/pull/3052#issuecomment-322010506
Martin Kolárik
@MartinKolarik
Aug 14 2017 19:52
publishing everything together would make updates very painful
you'd either end up will extremely frequent updates, or would have to wait with minor bug fixes to publish more of them at once
I think monorepo might work, but every plugin should be published separately
Joseph
@fskreuz
Aug 14 2017 19:55
I'm leaning towards the latter (scheduled releases) in the event of same-package publishing. But then that's just a wild idea. :D
Martin Kolárik
@MartinKolarik
Aug 14 2017 19:57
I can see the benefit of ensuring everything works together after update, but I think having everything in one repo would be enough for that
Joseph
@fskreuz
Aug 14 2017 20:05
So... independent versioning too (per package versioning)?
Was thinking of locking versions, so that i.e. ractive-load@0.10 implies that it works with ractive@0.10.
Martin Kolárik
@MartinKolarik
Aug 14 2017 20:07
yes I wanted to suggest that too
same major version (or minor before 1.0), but patches independent
Chris Reeves
@evs-chris
Aug 14 2017 21:01
that would effectively leave the semver for extra packages in the minor and patch fields, since the major would be tied to the ractive version, right?
Martin Kolárik
@MartinKolarik
Aug 14 2017 21:02
yes