Any idea why angular-mocks.js is not available on a CDN?

[David Karr]

I've noticed that although angular.js is available on a CDN (at least "ajax.googleapis.com"), that "angular-mocks.js" is not. It apparently was there at one time, but not in recent releases. Any idea why this is?

[Georgios Diamantopoulos]

My guess is it's because it's a file used for unit testing, not on production - so why include it in a CDN?

[David Karr]

Using CDN references instead of storing static copies seems like a good general practice, whether we're talking about deploying an app or testing it, unless you follow the rule of being able to run unit tests completely disconnected.  This is also a good thing.

If you can't make a CDN reference to angular-mocks.js or even angular.js from a karma-based unit test, which appears to be the case, then you have to have a downloaded copy of angular.js and angular-mocks.js, even if you use a CDN reference for angular.js in your deployable code.  This means that you'll have to make sure a version change in the CDN reference is followed by downloading a different version.

In any case, the question is moot, as it appears karma requires hardcoded paths to angular-mocks.js and other libs, so it can't do a CDN reference.

[Georgios Diamantopoulos]

If you're suggesting that a cdn://angular-latest.js is a generally good practice, I will have to disagree. 

Most CDNs I've seen don't provide these kind of pointers and even if they do I presume it's to be used with sites like plunkr.co

Why? Well, the cdn://latest.js will get auto updated to new versions and your app could break without notice.

In contrast, you have complete control over local libs, that are/should be version controlled too.

Also, having a CDN doesn't mean that the loading cannot fail or timeout - you should always keep a local static failover, just in case. 

With regards to keeping references in sync between the website and unit tests, how about NOT having the version number in the filename so that you DON'T have to update it every time?

Or, alternatively, pointing to a symlink directory that points to the right version. Updating the symlink updates both.

Or, using a script to insert the right version.

It all depends on your tooling and environment - a package manager makes a world of difference.

As you say, it's moot because karma needs local files, but perhaps these points will make you reconsider your CDN strategy.

Hope this helps

Georgios

[David Karr]

On Tuesday, October 1, 2013 2:01:07 PM UTC-7, Georgios Diamantopoulos wrote:

If you're suggesting that a cdn://angular-latest.js is a generally good practice, I will have to disagree. 

Most CDNs I've seen don't provide these kind of pointers and even if they do I presume it's to be used with sites like plunkr.co

Why? Well, the cdn://latest.js will get auto updated to new versions and your app could break without notice.

In contrast, you have complete control over local libs, that are/should be version controlled too.

I would never make a cdn reference to "latest", it would always specify the version, so it's not going to change without notice.
 

[Georgios Diamantopoulos]

OK, in which case one of the suggestions below should work for you.

---

Date: Tue, 1 Oct 2013 14:07:48 -0700
From: davidmic...@gmail.com
To: ang...@googlegroups.com
Subject: Re: [AngularJS] Re: Any idea why angular-mocks.js is not available on a CDN?

--
You received this message because you are subscribed to a topic in the Google Groups "AngularJS" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/angular/UF1OjYBJXpc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to angular+u...@googlegroups.com.
To post to this group, send email to ang...@googlegroups.com.
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/groups/opt_out.