You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// webpack.config.js// Configuring webpack-dev-server through https://nx.devconfig.devServer.allowedHosts.push('example.com');config.devServer.allowedHosts.push("chrome-extension://*")// Does not work.
Please paste the results of npx webpack-cli info here, and mention other relevant information
❯ yarn nx report ─╯
yarn run v1.22.11
$ nx report
> NX Report complete - copy this into the issue template
Node : 14.17.3
OS : darwin x64
yarn : 1.22.11
nx : Not Found
@nrwl/angular : Not Found
@nrwl/cli : 12.7.2
@nrwl/cypress : 12.7.2
@nrwl/devkit : 12.7.2
@nrwl/eslint-plugin-nx : 12.7.2
@nrwl/express : Not Found
@nrwl/jest : 12.7.2
@nrwl/linter : 12.7.2
@nrwl/nest : Not Found
@nrwl/next : 12.7.2
@nrwl/node : Not Found
@nrwl/nx-cloud : Not Found
@nrwl/react : 12.7.2
@nrwl/schematics : Not Found
@nrwl/tao : 12.7.2
@nrwl/web : 12.7.2
@nrwl/workspace : 12.7.2
@nrwl/storybook : 12.8.0
@nrwl/gatsby : Not Found
typescript : 4.3.5
✨ Done in 0.91s.
Expected Behavior
allowedHosts should support other protocols different than http(s).
Actual Behavior
allowedHosts does not support other protocols different than http(s).
For Features; What is the motivation and/or use-case for the feature?
Google created a new version of its extensions, it is called Manifest V3 https://developer.chrome.com/docs/extensions/mv3/intro/mv3-migration/
In that change, background pages, which used to be normal browser scripts, are now Service Workers, so its Origin is now chrome-extension://{id}
@montogeek for background tasks you should not use client, we recently had an issue for chrome extensions and I will provide fully working configuration for v4, but I can't found 😕
Code
Please paste the results of
npx webpack-cli info
here, and mention other relevant informationNx.dev report
Expected Behavior
allowedHosts
should support other protocols different than http(s).Actual Behavior
allowedHosts
does not support other protocols different than http(s).For Features; What is the motivation and/or use-case for the feature?
Google created a new version of its extensions, it is called Manifest V3 https://developer.chrome.com/docs/extensions/mv3/intro/mv3-migration/
In that change, background pages, which used to be normal browser scripts, are now Service Workers, so its Origin is now chrome-extension://{id}
This is how a request looks like now:
The text was updated successfully, but these errors were encountered: