how to? npm @types/* undeclared dependencies

[panva]

I would like to get advice on the following:

My module exports a Passport.js strategy, i publish on npm already and am looking to do jsr as well, it does not have a runtime dependecy on passport, nor express, but in the source is as follows, basically @types/express nor @types/passport is required to run the module but if the user has those installed (because he's also using express and passport) he's going to get the types necessary. I do not wish to add @types/* as a dependency.

import type * as express from 'express'
import type passport from 'passport'

export type VerifyFunctionWithRequest = (
  req: express.Request,
  /**
   * Parsed Token Endpoint Response returned by the authorization server with
   * attached helpers.
   */
  tokens: client.TokenEndpointResponse & client.TokenEndpointResponseHelpers,
  verified: passport.AuthenticateCallback,
) => void

Now, npx jsr publish --dry-run does not complain but I wonder what will happen when this is processed and published on jsr, will jsr users get their intellisense as expected (like they would if they installed via npm)

In that same vein I have a direct dependency on the jose and oauth4webapi modules. I keep those imports in the source code without specifiers but I added the following into jsr.json which I believe is going to rewrite the imports to their respective jsr distributions during publishing?

"imports": {
    "oauth4webapi": "jsr:@panva/oauth4webapi@^3.3.0",
    "jose": "jsr:@panva/jose@^6.0.1"
}

[AugustinMauroy]

have you take a look to :
https://docs.deno.com/runtime/fundamentals/node/#using-npm-packages

[panva]

Yes, are you suggesting something specific? I can't really add // @ts-types="npm:@types/express@^4.17" to the source as I intend the jsr distribution to not be tailored only for Deno users.

[AugustinMauroy]

actually I think it's the only way