-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firefox doesn't follow es module imports on transitions? (I think?) #7
Comments
Thought I was going crazy. Bummer, but good to know it's not just me. |
Any word on this? Guessing it'd be some sort of webpack tweak? |
Wondering if there's a way I can help with this issue. For me no Firefox support would be a blocker from releasing. (totally understand it's alpha right now, would love to help out where it makes sense) |
Did y'all change something? Clicking around the docs site works for me now (and it def did not before). |
+1 |
Looks like Firefox fixed their bug--whatever it was! |
- Add Cache-Control to /__remix_manifest responses - Don't call /__remix_data for routes that don't have data loaders - Remove location-based browser data cache, use built-in caching instead - Automatically reload the page when we detect the build has changed - Add `useBeforeUnload` hook for saving state immediately before reload - Add `json` and `redirect` helpers to `@remix-run/loader` Fixes #3 Fixes #4 Fixes #7 Fixes #15
Need to investigate further and will add more details, but just clicking around the docs page in firefox doesn't work. It imports the entries but then it doesn't follow the imports from there.
This is pretty low priority right now for us. We'll be creating a "nomodule" bundle with System.js for browser that don't support es modules, when we're in the think of things there we'll also investigate and fix this.
Until then however, if you have any ideas on why firefox won't follow the imports, let us know :)
The text was updated successfully, but these errors were encountered: