Fixing publint error and warning

[mikecousins]

The types field needs to be first in the exports object and no type is specified. This should fix all of the publint issues for the package.

Reference: https://publint.dev/@passageidentity/[email protected]

[sonarcloud]

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

[flanagankp]

@mikecousins I'll take a look at this PR soon, thanks for looking into this.

[flanagankp]

@mikecousins I've finally had a chance to take a look at this PR and it makes sense to me. I've also validated this place nicely with some common test apps, in particular ones that have been a little tricky in the past, namely:

• Next.js
• Remix
• Sveltekit
• The classic Express app

To actually merge this PR in you'll also need to add a changefile - we use a tool called beachball for semantic versioning. If you run npm run change on this branch you'll be guided through a dialog to set the type of change (just a patch), and add a note about the change that will get included in our changelog. The PR validation action will return an error until this is done.