angular/projects/shell-chrome/shell-chrome-webpack.config.js
Minko Gechev 54533bc037 fix(devtools): don't collide with the default runtime function (rangle/angular-devtools#6)
Currently, we don't inject `runtime.js` because we collide with the `runtime.js` of the host Angular application. This creates problems with non-Angular apps which don't use the same app bundling and the `backend.js` does not execute. This PR renames the runtime function to `___ngDevToolsRuntime`, which fixes the issue.

Additionally, since we support only Chrome this PR also drops differential bundling. We support the last two major versions of Chrome (look at `browserlist`), but if users require, we can easily extend the set of supported browsers.

Lastly, to have predictable file names, this PR also drops the hash suffix in the `shell-chrome` project.
2020-01-29 20:23:47 -05:00

11 lines
344 B
JavaScript

module.exports = {
entry: {
'content-script': 'projects/shell-chrome/src/app/content-script.ts',
background: 'projects/shell-chrome/src/app/background.ts',
backend: 'projects/shell-chrome/src/app/backend.ts',
devtools: 'projects/shell-chrome/src/devtools.ts',
},
output: {
jsonpFunction: '___ngDevToolsRuntime'
}
};