grafana/packages/grafana-runtime/src/index.ts

export * from './services';
export * from './config';
export { loadPluginCss, SystemJS } from './utils/plugin';
Add a @grafana/runtime package with backendSrv interface (#16533) grafana-runtime/tsconfig.json imports query to avoid a build error ¯\_(ツ)_/¯ 2019-06-03 23:55:59 +08:00			`export * from './services';`
@grafana/runtime: expose config and loadPluginCss (#17655) * move config to grafana runtime * set defaults * defaults in constructor * use @types/systemjs * rename Settings to GrafanaBootConfig 2019-06-20 02:31:47 +08:00			`export * from './config';`
grafana/runtime: Expose SystemJS from @grafana/runtime (#17927) In 4281344 the loadPluginCss util was migrated to @grafana/runtime package. This made SystemJS to fail loading the css files for a plugin. Root cause was that core and runtime used different SystemJS instances. To solve the issue, I am exposing SystemJS from @grafana/runtime package to make sure we are always using the same instance. Also, the SystemJS dependency was moved to runtime. 2019-07-04 19:32:09 +08:00			`export { loadPluginCss, SystemJS } from './utils/plugin';`