npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

angular-google-maps

v2.4.1

Published

AngularJS directives for Google Maps

Downloads

17,847

Readme

Project No longer actively maintained

With angular 2 and other competing projects we have decided to announce that this project is no longer activley maintained. If someone desires to take over the project please contact any of the admins.

As a warning this project is not activley watched by the admins and is checked here and there to fix any major issues. Therefore if something is major, contact someone directly via mentioning a users name/alias (will notify the user/admin).

Alternatives:

angular-google-maps

AngularJS directives for Google Maps Dependencies  Dependencies 

Builds:

  • Master (2.3.X): Build Status

  • 2.2.X: Build Status

  • 2.1.X: Build Status

  • 2.0.X: Build Status

task board: Stories in Ready

Gitter chat

 

NPM


Getting started

This is a set of directives and services for AngularJS ~1.0.7+, ^1.2.2+.

Dependencies

Please always be checking the package.json and bower.json. They are the spoken word and will usually be more up to date than this readme.

Tip use some library which will always pull in your dependencies (no matter what the changes are) to your vendor.js. IE: main-bower-files

Current Dependencies:

Development and or Running the Build

If you plan to hack on the directives or want to run the example, first thing to do is to install NPM dependencies:

npm install && bower install
  • Installing for Meteor application:
meteor add angularui:angular-google-maps
meteor npm install --save angular-google-maps

Building

To build the library after you made changes, simply run grunt:

grunt

If you get errors from jshint or specs, just add the --force argument.

Generating SourceMap(s)

grunt buildAll

This will generate source maps for development (angular-google-maps_dev_mapped.js) (non minified) and source maps to minified (angular-google-maps_dev_mapped.min.js) files. They each have their own corresponding map files. To get the coinciding source files you will need to copy the generated /tmp directory (currently not under scc).

Running the example

To run the example page, just run

grunt example

and open your browser on http://localhost:3000/example.html.

Documentation

The various directives are documented at official site.

Contributing

Filing issues: Prior to submitting an issue:

  • Search open/closed issues, src examples (./examples), gitter, and then google plus community! Again please search!
  • issues w/ plnkrs get attention quicker

Pull Requests (PR) more than welcome! If you're adding new features, it would be appreciated if you would provide some docs about the feature. This can be done either by adding a card to our Waffle.io board, forking the website branch and issuing a PR with the updated documentation page, or by opening an issue for us to add the documentation to the site.

PR's should follow angular git commit conventions.

Branching Scheme

PRS to master are for 2.3.X only.

If you want it rolled into a older release then target your PR to that respective branching name like 2.1.X.

Note: many fixes relevant to 2.0.X can be rolled up into 2.1.X, 2.2.X and 2.3.X

  • master: points to the active targeted next release branch (2.3.X)
  • 2.2.X: latest of 2.2.X
  • 2.1.X: ""
  • 2.0.X: "" ... etc