-
|
This is a pretty odd question, but I have the following route: export const loader: LoaderFunction = async ({ params }) => {
const postId = getParam(params, "postId") as PostId;
return new Response(`<!doctype html> <html> <body>Post id is: ${postId}</body></html>`, {
headers: {
"Content-Type": "text/html",
},
});
};I know this defeats the entire point of Remix, since I'm literally templating HTML, but there's a good reason. The full example is more complex. (I'm basically embedding another site after modifying its HTML on the server, it's almost like I turned a Chrome extension into a web page). This works fine, but I have an issue. If I do: What is a good workaround here? (Asides from sticking all the HTML in an iFrame, which I could do, but I don't want to do). |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
You could add |
Beta Was this translation helpful? Give feedback.
You could add
reloadDocumentto the Link or Form who triggered the loader/action that does the redirect, that way Remix will not navigate like a SPA