@granite-elements/granite-js-dependencies-grabber

A custom element to ensure that non-componentalized mon-modularized external JavaScript libraries are loader once and only once, and in the right order

Stats

StarsIssuesVersionUpdatedCreatedSize
@granite-elements/granite-js-dependencies-grabber
302.0.33 years ago3 years agoMinified + gzip package size for @granite-elements/granite-js-dependencies-grabber in KB

Readme

Published on webcomponents.org

granite-js-dependency-grabber

Based on Polymer 2.x

A custom element and a mixin to ensure that non-componentalized mon-modularized external
JavaScript libraries are loader once and only once, and in the right order, importing all the needed dependencies only if they aren't already loaded

Usage example

<granite-js-dependencies-grabber 
    id="granite-js-dependencies-grabber-demo"
    dependencies='[{"name":"moment","url":"../moment/min/moment.min.js"},{"name":"Chart","url":"../chart.js/dist/Chart.min.js"}]' 
    debug></granite-js-dependencies-grabber>

Install the Polymer-CLI

First, make sure you have the Polymer CLI installed. Then run polymer serve to serve your element locally.

Viewing Your Element

$ polymer serve

Running Tests

$ polymer test

Your application is already set up to be tested via web-component-tester. Run polymer test to run your application's test suite locally.

Contributing

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -m 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D

License

Apache Licence, Version 2.0

If you find any bugs or have a feature request, please open an issue on github!

The npm package download data comes from npm's download counts api and package details come from npms.io.