`loader` function doesn't have access to `context` after being redirected to

I load a route and check some things in the

loader

loader

function. If it errors, I

throw redirect

throw redirect

to another route. That route, however, doesn't seem to have access to the context in its

loader

loader

function.

routes/offers.tsx

...
loader: () {
  try {
    // some api call
  } catch (err) {
    throw redirect({ to: "/", search: { error: "missing_offer" } });
  }
}
...

...
loader: () {
  try {
    // some api call
  } catch (err) {
    throw redirect({ to: "/", search: { error: "missing_offer" } });
  }
}
...

routes/index.tsx

loader: async ({ deps, context, location }) => {
  console.log("loader", context); // loader is undefined!
}

loader: async ({ deps, context, location }) => {
  console.log("loader", context); // loader is undefined!
}

TanStack•2y ago•

10 replies

sour-pink

I load a route and check some things in the

loader

loader

function. If it errors, I

throw redirect

throw redirect

to another route. That route, however, doesn't seem to have access to the context in its

loader

loader

function.

routes/offers.tsx

...
loader: () {
  try {
    // some api call
  } catch (err) {
    throw redirect({ to: "/", search: { error: "missing_offer" } });
  }
}
...

...
loader: () {
  try {
    // some api call
  } catch (err) {
    throw redirect({ to: "/", search: { error: "missing_offer" } });
  }
}
...

routes/index.tsx

loader: async ({ deps, context, location }) => {
  console.log("loader", context); // loader is undefined!
}

loader: async ({ deps, context, location }) => {
  console.log("loader", context); // loader is undefined!
}