💎 Release new version 2.6.0

🔥 Breaking Change

• Update release build to not include externals. #84

Release builds

If you're using the browser version directly from unkpg there is no action required
If you're using Webpack 1 / Webpack 2 / Browserify you will need to install Chart.js

yarn add chart.js

Both Vue.js and Chart.js are now peerDependencies and excluded from the bundled files. This way if Vue.js or Chart.js updates you can use the latest version without updating or waiting for an update of vue-chartjs .

Explanation of Different Builds

There are three different entry points. It depends on which build setup do you have. The dependencies are bundled or required as a peerDependency.

• Browser
• Browserify / Webpack 1
• Webpack 2

Build	Chart.js	Vue.js
vue-chartjs.full.js	Bundled	Bundled
vue-chartjs.full.min.js	Bundled	Bundled
vue-chartjs.js	peerDependency	peerDependency
vue-chartjs.min.js	peerDependency	peerDependency
es/index*	peerDependency	peerDependency

Browser

You can use vue-chartjs directly in the browser without any build setup. Like in this codepen. For this case, please use the vue-chartjs.full.min.js which is the minified version. It has Vue.js and Chart.js bundled into it. And bundled to a UMD Module. So you only need that one file.

Browserify / Webpack 1

If you're using Gulp, Browserify or Webpack 1 the entry is vue-chartjs.js which is transpiled and bundled UMD Module.

However Vue.js and Chart.js are deerDependencies so you have to install them seperately. In most projects you will have Vue.js already installed anyways. This way, you can have different versions of Vue.js and Chart.js then in this package.

Webpack 2

If you're using Webpack 2 it will automatically use the jsnext:main / module entry point. Which is es/index.js
It is a transpiled es version of the source. And is not bundled to a module. This way you three shaking will work. Like in the bundled version, Vue.js and Chart.js are peerDependencies and need to be installed.

Pre-release 2.6.0-rc1

🔥 Breaking Change

• Update release build to not include externals. #84

Testing

If you want to test the build you can install it over

yarn add vue-chartjs@next or yarn add [email protected]

Release builds

If you're using the browser version directly from unkpg there is no action required
If you're using Webpack 1 / Webpack 2 / Browserify you will need to install Chart.js

yarn add chart.js

Both Vue.js and Chart.js are now peerDependencies and excluded from the bundled files. This way if Vue.js or Chart.js updates you can use the latest version without updating or waiting for an update of vue-chartjs .

Explanation of Different Builds

There are three different entry points. It depends on which build setup do you have. The dependencies are bundled or required as a peerDependency.

• Browser
• Browserify / Webpack 1
• Webpack 2

Build	Chart.js	Vue.js
vue-chartjs.full.js	Bundled	Bundled
vue-chartjs.full.min.js	Bundled	Bundled
vue-chartjs.js	peerDependency	peerDependency
vue-chartjs.min.js	peerDependency	peerDependency
es/index*	peerDependency	peerDependency

Browser

You can use vue-chartjs directly in the browser without any build setup. Like in this codepen. For this case, please use the vue-chartjs.full.min.js which is the minified version. It has Vue.js and Chart.js bundled into it. And bundled to a UMD Module. So you only need that one file.

Browserify / Webpack 1

If you're using Gulp, Browserify or Webpack 1 the entry is vue-chartjs.js which is transpiled and bundled UMD Module.

However Vue.js and Chart.js are deerDependencies so you have to install them seperately. In most projects you will have Vue.js already installed anyways. This way, you can have different versions of Vue.js and Chart.js then in this package.

Webpack 2

If you're using Webpack 2 it will automatically use the jsnext:main / module entry point. Which is es/index.js
It is a transpiled es version of the source. And is not bundled to a module. This way you three shaking will work. Like in the bundled version, Vue.js and Chart.js are peerDependencies and need to be installed.

💎 Release new version 2.5.6

Updates Dependencies

• cb51f2a [email protected]

💎 Release new version 2.5.5

Update Dependencies

• Vue.js
• Dev Dependencies

💎 Release new version 2.5.4

Fixed

• remove browser field from package.json

💎 Release new version 2.5.3

Browser compatible version

• Add umdNamedDefine to webpack conf
• Add minified version

💎 Release new version 2.5.2

😔 Nothing new.

• Vue.js updated to 2.2.4

💎 Release new version 2.5.1

Fixed

• #58 Added lodash as dependency because of the unbundled esm files.

💎 Release new version 2.5.0

⚠ Potential Breaking Changes ⚠

• #56 Seperate horizontal bar from bar chart component

If you're using horizontal barcharts:

The horizontalBar got seperated into a own component.
The problem was, that if you're using the reactiveMixin the type gets overwritten.

As the mixin calls renderChart() if new datasets arrive. But there is no way to add the type.
The BarChart had a unuqie render parameter renderChart({data}, {options}, type).

Before

import {Bar} from 'vue-chartjs'

export default Bar.extend({
  props: ['data', 'options'],
  mounted () {
    this.renderChart(this.data, this.options, 'horizontalBar')
  }
})

Now

import {HorizontalBar} from 'vue-chartjs'

export default HorizontalBar.extend({
  props: ['data', 'options'],
  mounted () {
    this.renderChart(this.data, this.options)
  }
})

💎 Release new version 2.4.1

Updated dist files

It seems that some tools have problem with building es6 files out of node_modules.
For this reason, I changed the main entry back to the bundled umd file: dist/vue-chartjs.js.

Added transpiled es6

I also added a transpiled es version which is under the folder es/ and contains all source files transpiled for jsnext:main.

Additional entries

• The module and jsnext:main entrypoint is now the fully transpiled src under es/index.js.

Modern tools like webpack 2, rollup etc. will get the jsnext:main entry so you will be using the unbundled files.