Fix importing from Passage-Node

[flanagankp]

Description

The main export from Passage-Node was not behaving well in scenarios using more modern ESM tools like Vite in the context of things like SvelteKit and Remix. This was due to a couple of issues that have been resolved:

• Package.json was not properly using the more modern exports field to differentiate between CJS and ESM builds
• The ESM build was not being transformed properly so it had a module syntax error, resolved by using the tsup esbuild toolchain like we use in passage-js that has been well tested and understood (long term we should look into vite as the build tool but I've only ever used it to target browsers so didn't want to experiment with that yet for the node build).

Now you can use the package properly in modern frameworks like Sveltekit both of these ways:

• import { Passage } from '@passageidentity/passage-node' (which we should push people to do as in the next major release I want to only support this option)
• import Passage from '@passageidentity/passage-node'
  And in older contexts that don't use ES modules the following works
• const { Passage } = require('@passageidentity/passage-node'); (again what we'll go with long term)
• const { Passage } = require('@passageidentity/passage-node').default; (what you currently have to do)

Jira Story

PSG-4297

Images/Screen Capture

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Only
• This change requires a documentation update

Testing

• Tested local package build against Sveltekit using import Passage from '@passageidentity/passage-node syntax
• Tested local package build against Sveltekit using import { Passage } from '@passageidentity/passage-node' syntax
• Tested local package build against Remix using import Passage from '@passageidentity/passage-node syntax
• Tested local package build against Remix using import { Passage } from '@passageidentity/passage-node' syntax
• Tested local package build against pure-JS express app using const Passage = require('@passageidentity/passage-node') syntax
• Tested local package build against pure-JS express app using const { Passage } = require('@passageidentity/passage-node') syntax

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud