Service worker script errors if run in chrome extension

Is this a bug report?

Bug

Can you also reproduce the problem with npm 4.x?

Unrelated

Which terms did you search for in User Guide?

chrome

Environment

1. node -v: 8.5.0
2. npm -v: 5.4.0
3. yarn --version (if you use Yarn):
4. npm ls react-scripts (if you haven’t ejected): 1.0.13

Then, specify:

1. Operating system: Ubuntu 16.04
2. Browser and version (if relevant): Chrome 61

Steps to Reproduce

• Run compiled app as chrome extension

Expected Behavior

• No errors in console

Actual Behavior

Uncaught (in promise) TypeError: Request scheme 'chrome-extension' is unsupported
    at service-worker.js:1
    at <anonymous>

[jeffposnick]

This is what I’d expect if you attempt to register a service worker that intercepts requests for chrome-extension: URLs. The service worker can’t respond to to those types of requests, and there’s an error logged suggesting as much.

Chrome has its own approach to installing/caching the resources needed to display a Chrome Extension. Service workers don’t fit into that picture.

The message in the console can be safely ignored (it’s not going to affect your extension’s functionality), and to prevent it from showing up in the future, you can modify your index.js to remove the registerServiceWorker() call.

There’s also an unregister function that you could optionally add in to your index.js if you’ve deployed this publicly and want to “clean up” the noise from the previous non-functionality registration.

[jeffposnick]

// Inside index.js:
import {unregister} from './registerServiceWorker';
unregister();