If it's just a general library to use anywhere, then sure build it with no dependencies. But if it's a library intended for Angular then the library would be b

If it's just a general library to use anywhere, then sure build it with no dependencies. But if it's a library intended for Angular then the library would be built with Angular as a dependency, much like it would be with jQuery. I don't see a negative with a library being built that has dependencies if it is intended to be used in conjunction with the thing it is depending upon, since in most likelihood a like-minded developer is already using it.