Uncaught (in promise) SyntaxError: Unexpected token export 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

[peterennis]

Stencil version: (run npm list @stencil/core from a terminal/cmd prompt and paste output below):

C:\ae\adaept.com\aepwa>npm list @stencil/core
@stencil/starter@0.0.1 C:\ae\adaept.com\aepwa
`-- @stencil/core@0.7.24

I'm submitting a ... (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or https://stencil-worldwide.slack.com

Current behavior:

Expected behavior:
No errors

Steps to reproduce:
Latest version

Related code:

Other information:
https://aepwa-dev.firebaseapp.com/

[Dominic Böttger]

Same problem here after checking out the current repository.

Uncaught (in promise) SyntaxError: Unexpected token {
    at Object.<anonymous> (workbox-core.dev.js:954)
    at Generator.next (<anonymous>)
    at step (workbox-core.dev.js:14)
    at workbox-core.dev.js:25

const{h:t}=window.App;import{createThemedClasses .......

I also tried older version of stencil/core, but i get the same result.

[Justin Willis]

Hey! This is actually a chrome issue https://bugs.chromium.org/p/chromium/issues/detail?id=810469 . I responded to this issue to get it prioritized with the Chrome team and will be opening a new one if this one does not get any responses.

[peterennis]

https://bugs.chromium.org/p/chromium/issues/detail?id=810469

This is marked as "WONTFIX" ???

It links to here:

GoogleChrome/workbox#1433 (comment)

Then this points to a new issue opened by @jeffposnik

https://bugs.chromium.org/p/chromium/issues/detail?id=833501

@jgw96 - I do not see anything from you. . .

[Jonathan Holt]

@peterennis https://bugs.chromium.org/p/chromium/issues/detail?id=810469#c4 is @jgw96 comment

[Jamrelian]

@jgw96 @peterennis They have been merged into issue 832202, so the new URL is
https://bugs.chromium.org/p/chromium/issues/detail?id=832202

Indeed, it's a Chrome issue, can be reproduced using standard Cache API instead of Workbox (https://github.com/hwalab-developer/swesmit).