Constructor call fails in a Remix app

[mikecousins]

Attempting to move my Remix app over to Passage. The react package seems to be working okay for the client side and I'm getting the cookie stored properly. I'm having issues on the server side though.

I get this error:

TypeError: __vite_ssr_import_2__.default is not a constructor

Executing this code:

// /app/models/session.server.ts
import Passage from '@passageidentity/passage-node';

// other code

  const passage = new Passage({
    appID: process.env.PASSAGE_APP_ID ?? '',
    apiKey: process.env.PASSAGE_API_KEY,
    authStrategy: "HEADER",
  });
  const userId = await passage.authenticateRequest(request);

Feels like potentially an ESM issue? I do notice that your package has pretty messed up types that might be causing it. This is the linter that I usually use to debug my packages: https://publint.dev/@passageidentity/passage-node@2.10.1

[softbeehive]

Also in Astro (SSR mode)

__vite_ssr_import_1__.default is not a constructor

Middleware

// src/middleware.ts

import { defineMiddleware } from 'astro:middleware'
import Passage, { type PassageConfig } from '@passageidentity/passage-node'

export const onRequest = defineMiddleware(async (context, next) => {
  if (context.url.pathname === '/plan') {
    const passageConfig: PassageConfig = {
      appID: process.env.PASSAGE_APP_ID,
    }
    try {
      const passage = new Passage(passageConfig)
      const userID = await passage.authenticateRequest(context.request)
      context.locals.userID = userID
      return next()
    } catch (error) {
      console.log('PASSAGE ERROR', error)
      return new Response('Unauthorized', { status: 401 })
    }
  }
  return next()
})

[apobletts]

Thanks for the issue report. We are looking into a fix or a workaround for these frameworks and I'll get back to you soon.

[baraakamal]

Facing the very same issue with Sveltekit

TypeError: __vite_ssr_import_2__.default is not a constructor

[flanagankp]

This importing issue has been resolved as of v2.11.0 of the package. I'd also recommend updating your import statement to using named import syntax as that is what we will be exclusively using in the next major version:
import { Passage } from '@passageidentity/passage-node'