Run any basic SSR app as normal and compare the instance opened on Chrome and on Safari. I keep seeing this console message in the Chrome browser:
Refused to execute script from 'http://localhost:4322/main.dart.js' because its
MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
However, everything seems to work fine on Chrome. The server/client side code work as expected.
Safari MacOS
With the app still running, open in a Safari browser on MacOS. Things are more catastrophic here and the server actually responds with a 500 (Internal Server Error).
The Content-Type warning may be a clue as to why this may be happening and why the server error only happens on Safari.
Browser Console
[Error] Failed to load resource: the server responded with a status of 500 (Internal Server Error) (app.client.dart.bootstrap.js, line 0)
[Error] Refused to execute http://localhost:8080/@http://localhost:8080/components/app.client.dart.bootstrap.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Error: Script error for "app.client.dart.bootstrap"
http://requirejs.org/docs/errors.html#scripterror
defaultOnError (require.js:143)
onError (require.js:549)
onScriptError (require.js:1738)
Jaspr Server
[SERVER] [ERROR] GET /@http://localhost:8080/components/app.client.dart.bootstrap.js
[SERVER] [ERROR] Error thrown by handler.
[SERVER] [ERROR] FormatException: Scheme not starting with alphabetic character (at character 1)
[SERVER] [ERROR] @http://localhost:8080/components/app.client.dart.bootstrap.js
[SERVER] [ERROR] ^
[SERVER] [ERROR] dart:core _SimpleUri.resolve
[SERVER] [ERROR] package:shelf_proxy/shelf_proxy.dart 42:28 proxyHandler.<fn>
[SERVER] [ERROR] package:jaspr/src/server/server_handler.dart 74:32 _proxyHandler.<fn>
Chrome
Run any basic SSR app as normal and compare the instance opened on Chrome and on Safari. I keep seeing this console message in the Chrome browser:
However, everything seems to work fine on Chrome. The server/client side code work as expected.
Safari MacOS
With the app still running, open in a Safari browser on MacOS. Things are more catastrophic here and the server actually responds with a
500 (Internal Server Error)
.The
Content-Type
warning may be a clue as to why this may be happening and why the server error only happens on Safari.Browser Console
Jaspr Server
Reproduce
Steps To Reproduce
Doctor Output