Export the vega API

[pschmiedel]

Currently, it is not possible to call vega APIs directly (e.g. vega.scheme) when using the minified version of vue-vega. Simply importing from vega and calling the API has no effect, since it is a different file (from node_modules/vega* instead of the minified file) with a different scope.

This could probably be remedied by something like this (in index.js):

export * from 'vega'

That way we could use the following to access the API in the same scope:

import { scheme } from 'vue-vega'
scheme('my-scheme', [ ... ])

Alternatively, something like this could be used:

import * as vega from 'vega'
export { vega }

import { vega } from 'vue-vega'
vega.scheme('my-scheme', [ ... ])

[nesterone]

Hi, @pschmiedel

Could you make it more clear on which API methods you not able to use?

vue-vega is just an adapter around vega View

Right now I expose only one default object with install, mapVegaLiteSpec, and VueVegaLiteComponent, however, in near future, I want to leave only vue plugin as default object and other entities would go as ordinary exports

Meanwhile I have a #6, to exclude vega and vega-lite from budle

[pschmiedel]

As I wrote above, e.g. vega.scheme. Another one would be the Locale API. It's not possible because there is no way to get to the same "vega object" instance (more accurately, the vega scope) that is used in your bundled code. Anyway, I'm using the default vega-embed package now, which seems to work fine.

[nesterone]

I see, few questions if you don't mind ;)

Did you use vega embedded with some vue component wrapper?

I didn't touch vega schemas and other global vega configs yet, however as potential library consumer what do you think about next approach ?

import Vue fron 'vue'
import vega from 'vega'
import VueVega from 'vue-vega'

// vega global configs 
vega.scheme({/* collor here */})

Vue.use(VueVega, { vega })

[pschmiedel]

No, I just used vega-embed without any vue wrapper.

Your approach could work however there are the following issues:

• it means the vega library is potentially included twice in the output generated by e.g. weback (once from vue-vega.min.js and once from node_modules/vega)
• it allows using a different version of vega than the one bundled with vue-vega (potential version conflict)
• it is one more import statement than simply import { default as VueVega, vega } from 'vue-vega'

Btw vega-embed does in fact export the imported vega object again.