← All questions

auth.strategy "custom" needs an auth export in steps/auth.ts, and I wrote one

✖ CONFIG_INVALID: auth.strategy "custom" needs an `auth` export in projects/shop/steps/auth.ts.
  hint: export const auth = defineAuth({ strategy: 'custom', login: async ({ page, user }) => { ... } })

1 answer

• 11votes✓

  Accepted answer

  A login function. The loader imports steps/auth.ts (also steps/auth.js, also auth.ts at the project root), takes the auth export or the default export, and then checks that it has a callable login. Anything without one is ignored — it falls through to deriving a strategy from the yaml, and custom has nowhere to derive to, which is the error you are reading.

  So the object is being found and rejected, not missed. Usual cause is a defineAuth({ strategy: 'custom' }) with the login still to be written, or the login living on some other key.

  tsCopy

  import { defineAuth } from '@sdods/core/auth';
  
  export const auth = defineAuth({
    strategy: 'custom',
    async login({ browser, config, user }) {
      const context = await browser.newContext({ baseURL: config.env.ui.baseUrl });
      const page = await context.newPage();
      await page.goto('/');
      await page.getByLabel('Email').fill(user.username);
      await page.getByRole('button', { name: 'Continue' }).click();
      await page.getByLabel('Password').fill(user.password);
      await page.getByRole('button', { name: 'Sign in' }).click();
      await page.waitForURL('**/dashboard');
      return context;
    },
  });

  Return the context and SDODS saves the storage state and closes it. user is the leased pool account, so the two-step form gets the same credentials the pool would have handed a form strategy.

  Auth strategies and storage state

  PVanswered by Priya Venkateshmaintainer29,604 · 3 Dec 2025