Using Bower Dependencies

❗ As of NodeCG v0.9, per-bundle bower and npm dependencies are no longer automatically installed. It is up to the user to run whatever installation commands are necessary in each bundle.

NodeCG makes your bundle's Bower dependencies available from /bundle/:bundleName/bower_components/*. This route matches the structure of the filesystem, so you will be able to take advantage of your IDE's autocomplete functionality.

<link rel="stylesheet" href="../bower_components/other-component/style.min.css">
<script src="../bower_components/some-component/lib.min.js"></script>
...

.. though you can the absolute paths if needed:

<script src="/bundles/my-bundle/bower_components/some-component/lib.min.js"></script>

If you need to access NodeCG's own Bower dependencies, they are available from the absolute /bower_components/* route. This is not recommended. Any dependencies that your bundle needs should be part of your bundle's bower.json, because NodeCG's Bower dependencies are subject to change without warning.

<!-- Loads NodeCG's copy of the webcomponents.js Polyfill -->
<script src="/bower_components/webcomponentsjs/webcomponents-loader.js"></script>