We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://remix-firebase-test.vercel.app/about
https://github.com/jdgamble555/remix-firebase-test/tree/master
https://stackblitz.com/github/jdgamble555/remix-firebase-test
The stackblitz seems to work fine. The problem is ONLY in production. You can test this on a local machine by running:
ONLY
npm run build
npm run start
Pushed to Vercel, Brand new remix - 2.8.1
npm
This is a basic app. All I have installed is Tailwind.
It should just display the route as working in the dev version.
dev
It says 404 not found, the server loads correctly, but the browser routing is not correct.
The text was updated successfully, but these errors were encountered:
override rollup to 4.15.0, this is rollup issue.
Sorry, something went wrong.
Since rollup is in the core package though, Remix should upgrade their dependencies. But yes, this fixed the problem.
rollup is not in the core package, it's a nested dependency of vite. The rollup folks are looking into this and have a fix open: rollup/rollup#5443 (comment).
rollup
vite
Closing as a duplicate of #9275
Resolved in rollup 4.16.2: https://github.com/rollup/rollup/releases/tag/v4.16.2
No branches or pull requests
Reproduction
https://remix-firebase-test.vercel.app/about
https://github.com/jdgamble555/remix-firebase-test/tree/master
https://stackblitz.com/github/jdgamble555/remix-firebase-test
The stackblitz seems to work fine. The problem is
ONLY
in production. You can test this on a local machine by running:npm run build
npm run start
System Info
Used Package Manager
npm
This is a basic app. All I have installed is Tailwind.
Expected Behavior
It should just display the route as working in the
dev
version.Actual Behavior
It says 404 not found, the server loads correctly, but the browser routing is not correct.
The text was updated successfully, but these errors were encountered: