Skip to content

missing a solution for non-declared typings dependencies #989

Open
@panva

Description

@panva

I've just published https://jsr.io/@panva/openid-client and I had to forego publishing one of its entrypoints, namely its passport strategy implementation.

The problem i encountered is that express and passport from which only types are imported cannot be resolved. I am not keen on adding these modules as dependency in jsr.json because not all users use the passport strategy and those who do (and care about types) must have their respective types installed already, and for those who don't care about passport (large amount of users) I don't wish to incur the dependency.

The original failed publish details https://jsr.io/status/e496c2cf-23ea-4d34-b08d-0488cff185b5, it is important to note that this failed on the server but locally npx jsr publish --dry-run did not fail, which made hopeful this wouldn't happen.

The ask: how should this be dealt with? This module and this entrypoint is happily published and used from npm without these dependencies.

Relates to #978

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Needs Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions