Fix Vue wrapper packaging issue

[moores2]

Fixes #231

• Set main for package correctly
• Export \src and \dist to package, so that individual components can be imported by clients (like the React wrappers do).

Note: the vue-cli library build generates and extraneous dist/demo.html that does not work. There is an issue for this here: vuejs/vue-cli#3291

Review checklist (for reviewers only)

• Demos all features
• Documented/annotated
• Matches UI/UX specs
• Meets the code style guide
• Accessible
• Mobile first (responsive)
• RTL support (bidirectional text)
• Performant (limited bloat)

[netlify]

Deploy preview for carbon-charts ready!

Built with commit 9b69345

https://deploy-preview-236--carbon-charts.netlify.com

[theiliad]

Hi,
When released, the JS files are not in the dist directory anymore, but in root:

Also, did you see #231 (comment)? Would adding the ./src directory to the published package fix that? We should also have a bundle that includes everything in itself without the need of the ./src folder

[cal-smith]

Looks good generally 👍 just a couple tweaks due to some build/deploy changes we've implemented

[theiliad]

@moores2 We need to modify build.sh for the vue package now to include src:
https://github.com/carbon-design-system/carbon-charts/blob/master/packages/vue/build.sh

[cal-smith]

from my comment here: #231 (comment)

do we need so ship src/? I figure it best to just let consumers deal with the compiled JS ... especially with Vue, consumers really don't get anything by having it available.

[theiliad]

Yeah it would be preferable if we have a bundle that exports modules separately, and one that includes all where dev can use it through CDNs

[moores2]

I have reworked index.js with a simpler approach, and added exports so that the source is not needed in the shipped package. This update should allow clients to load the wrappers in 2 ways:

Firstly, to just load all of the chart components globally into Vue by using a Vue plug-in, like this:

import Vue from 'vue';
import chartsVue from '@carbon/charts-vue';
...
Vue.use(chartsVue);
...
export default {
...
  template:
    '<ccv-bar-chart :data="barData" :options="barOptions"></ccv-bar-chart>'

The second option is to allow consumers to selectively import just the wrappers/components that they want, like this:

<template>
  ...
  <ccv-bar-chart :data="barData" :options="barOptions"></ccv-bar-chart>
  ...
</template>

<script>
import { CcvBarChart } from "@carbon/charts-vue";

export default {
  ...
  components: { CcvBarChart },
  ...
};
</script>

[cal-smith]

Awesome! 🎉 LGTM

re-reqesting

[theiliad]

@moores2 @cal-smith This looks good 💯
Do we need any changes in the deploy scripts for the correct bundles/files/directories to be picked up?

[cal-smith]

Nope we're good to go 👍

[cal-smith]

Merging