New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 810469 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Caching a JS file with an export result in an error (possibly other JS syntaxes)

Reported by matt.t.g...@gmail.com, Feb 8 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0

Steps to reproduce the problem:
1. Go to https://morning-landmine.glitch.me/
2. Open the console and notice the logs and errors

Source Code: https://glitch.com/edit/#!/morning-landmine?path=views/index.html:30:6

What is the expected behavior?
The "module.js" file should be cachable in the window and the service worker.

What went wrong?
The service worker throws an error in Chrome 65 "Uncaught (in promise) SyntaxError: Unexpected token export".

(Not this is just **caching** the file - not running it)

Did this work before? N/A 

Chrome version: 65.0.3325.51 (Official Build) dev (64-bit)  Channel: n/a
OS Version: 
Flash Version:
 

Comment 1 by ajha@chromium.org, Feb 9 2018

Labels: Needs-Triage-M65
Cc: vamshi.k...@techmahindra.com
Labels: Needs-Feedback Triaged-ET
Thanks for filing the issue!

Unable to reproduce the issue on reported chrome version 65.0.3325.51 and on the latest Dev  66.0.3343.0 using Ubuntu 14.04 with the below mentioned steps.
1. Launched chrome
2. Navigated to https://morning-landmine.glitch.me/
3. Opened DevTools->Console
We are unable to see any error and the file cached service worker. Attaching the screenshot of the same.

@Reporter: Could you please check the screenshot and let us know if we have missed any steps while reproducing the issue. Any further inputs from your end may help us to triage the issue in a better way.

Thanks!
810469.png
138 KB View Download
Status: WontFix (was: Unconfirmed)
Not reproducible.

Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested.

Comment 4 by jus...@ionic.io, Apr 13 2018

Hello all! I am still able to reproduce this issue on Chrome 65 on Windows 10.

Steps to reproduce the problem:
1. Go to https://morning-landmine.glitch.me/
2. Open the console and notice the logs and errors

We are also running into this issue with sites such as https://stenciljs.com/ which use dynamic imports of ES modules. This issue does not seem to happen with modules included through `<script type='module' />`, only with modules imported using dynamic imports.

Chrome Version: 65.0.3325.181 (Official Build) (64-bit) (cohort: Stable)
OS Version: Windows 10 Pro version 1803

Comment 5 by jus...@ionic.io, Apr 13 2018

Also another piece of info, I have to refresh the page to get the error with the original repro case.
Same problem here.

Chrome version: 65.0.3325.181
OS: Windows 10

Error:
module.js:1 Uncaught (in promise) SyntaxError: Unexpected token export
    at fetch.then (sw.js:6)
fetch.then @ sw.js:6
Same problem here with a Firebase Hosting:

http://web-photo-filter.firebaseapp.com

Repo/source code:

https://github.com/peterpeterparker/web-photo-filter

Chrome 65, problem on both Mac and PC


Same problem here, with a GitHub Pages hosting, and the Workbox service worker library:

https://helloesm.hwalab.com/

Repository source code:

https://github.com/hwalab/helloesm

Google Chrome 65.0.3325.181 (Official Build) (64-bit) on Windows 10 Home 10.0.16299 Build 16299


app.js:6 Uncaught (in promise) SyntaxError: Unexpected identifier
    at Object.<anonymous> (workbox-core.prod.js:1)
    at Generator.next (<anonymous>)
    at n (workbox-core.prod.js:1)
    at workbox-core.prod.js:1

The service worker fails to activate ("is redundant"), and the Chrome Lighthouse audit tool reports that "user will not be prompted to install the Web App".

On Chrome 65.0.3325.109 on Android 7.0, the Add to Home screen option, which used to install the PWA in the past, after refresh now it only offers to add it as a simple shortcut.

More details and screenshots in this Workbox issue comment:
https://github.com/GoogleChrome/workbox/issues/1433#issuecomment-381656479

Comment 9 by jeffy@google.com, Apr 16 2018

Given that this issue is marked as WontFix, I've opened up https://bugs.chromium.org/p/chromium/issues/detail?id=833501 with some more recent details.

Sign in to add a comment