Update components build tools. about dash-bootstrap-components

[pbugnion]

Thanks for submitting this! @tcbegley -- I'm happy to look at this since I put some of the initial infrastructure in place.

[pbugnion]

@T4rk1n Under what conditions do _js_dist["dev_package_path"] and _js_dist["external_url"] get used?

At the moment, we don't publish dash_bootstrap_components to NPM, so having a link to unpkg seems a bit meaningless. While we do want to publish to NPM, I think we will probably publish a bundle that is optimized for building additional JS components, not as a faithful representation of the current bundle.

[T4rk1n]

They are optional keys.

• dev_package_path is used for serving the dev bundle for debugging the front end and more dev features. It is served when the key is found in _js_dist and app.run_server(debug=True).
• external_url is used when found in the _js_dist and app.scripts.config.serve_locally=False, it is the current default of dash when found.
• relative_package_path is the main path to the local resources and used by default when other conditions are false.

So if you don't want to publish on npm just don't include the external_url, with dash 1.0.0 the default will be to serve the resources locally.

[pbugnion]

Perfect, thank you for the explanation.

I suggest we try to include a dev bundle, probably as a new PR separate to #94.

[pbugnion]

I've opened issue #100 for creating a development bundle. Everything else in this issue is addressed in PR #94, so I'm closing this.

Thanks for your help!