grafana/runtime: Expose SystemJS from @grafana/runtime (#17927)
In 42813448 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.
Showing
... | ... | @@ -109,8 +109,6 @@ |
"sass-loader": "7.1.0", | ||
"sinon": "1.17.6", | ||
"style-loader": "0.23.1", | ||
"systemjs": "0.20.19", | ||
"systemjs-plugin-css": "0.1.37", | ||
"terser-webpack-plugin": "1.2.3", | ||
"ts-jest": "24.0.2", | ||
"ts-loader": "5.3.3", | ||
... | ... |
... | ... | @@ -16,7 +16,10 @@ |
}, | ||
"author": "Grafana Labs", | ||
"license": "Apache-2.0", | ||
"dependencies": {}, | ||
"dependencies": { | ||
"systemjs": "0.20.19", | ||
"systemjs-plugin-css": "0.1.37" | ||
}, | ||
"devDependencies": { | ||
"@types/systemjs": "^0.20.6", | ||
"awesome-typescript-loader": "^5.2.1", | ||
... | ... |
Please
register
or
sign in
to comment