Igor seemed interested in the prospect of preserving the existence of a
single “distribution” of Angular (hence my previous comments about UMD).
IMO, even in spite of UMD’s drawbacks, this allows us to ship a single
Angular release immediately, with no surprises for existing users.
Any breaking changes (such as publishing a CJS-only version of Angular on
NPM) would need to go in 1.4.
At the end of the day, we want developers to be able to npm install angular,
write require('angular'), and have it work without any surprises.
~Andrew
On Tuesday, January 20, 2015 at 5:07:42 PM UTC-5, Caitlin Potter wrote:
We’re sort of making it up as we go — but the main goal is to have multiple
> core team members say “sounds good, lets do that”. There’s no real “time
> limit”, but things would move faster if we got there within a week.
>
> There are a few things blocking this:
>
> For me, I want to figure out solid conventions that will satisfy people,
> so that we aren’t shipping anything unexpected or surprising. It should fit
> nicely into browserify users workflow.
>
> Igor sounded like he wasn’t keen on making it the “default” npm release,
> since it technically changes things for people who were happily using what
> was shipped on npm already.
>
> There might have been other issues, I’m going from memory here =)
>
> Most of the discussion does seem to be circling around things which are a
> bit out of scope for this topic, but it was bound to happen. It would
> definitely be helpful to focus on what will best serve angular developers
> within the scope of CJS support on npm, though.
>
> On Jan 20, 2015, at 5:00 PM, Paul Everitt <[email protected]
> <javascript:>> wrote:
>
> Just out of curiosity, what's the process on this discussion period? Is
> there an end date for when input is finished? I'd love for this to get into
> the 1.4 release cycle, or even 1.3.x if there's going to be another release.
>
> Are there points from Pete's two notes that need to be digested?
>
> --
> You received this message because you are subscribed to the Google Groups
> "AngularJS" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected] <javascript:>.
> To post to this group, send email to [email protected] <javascript:>
> .
> Visit this group at http://groups.google.com/group/angular.
> For more options, visit https://groups.google.com/d/optout.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
