fix: include oauth2-redirect.js in npm package distribution

[1234-ad]

Fix for Issue #10574: Include oauth2-redirect.js in npm package

Problem

The oauth2-redirect.js file was missing from the npm package distribution, causing OAuth2 authentication to fail when using the npm package. The file exists in the repository and is referenced by oauth2-redirect.html, but wasn't being packaged.

Root Cause

The .npmignore file uses a whitelist approach (excluding everything with * and then including specific files with !). It included !dist/oauth2-redirect.html but was missing !dist/oauth2-redirect.js.

Solution

Added !dist/oauth2-redirect.js to the .npmignore file whitelist.

Changes Made

• .npmignore: Added !dist/oauth2-redirect.js to ensure the file is included in npm packages

Verification

After this fix, npm pack swagger-ui will include both:

• ✅ dist/oauth2-redirect.html (already included)
• ✅ dist/oauth2-redirect.js (now included)

Impact

• ✅ Fixes OAuth2 authentication when using npm package
• ✅ No breaking changes - purely additive
• ✅ Maintains backward compatibility
• ✅ Simple, targeted fix with minimal risk

Testing

The fix can be verified by:

1. Running npm pack swagger-ui
2. Checking that oauth2-redirect.js is now included in the package contents
3. Confirming OAuth2 flows work properly with the npm package

This is a critical fix for OAuth2 functionality that was broken due to missing file packaging.

Fixes #10574

[glowcloud]

Hi @1234-ad,

Thanks for the contribution! The fix looks good, but could you please remove the additional FIX_DOCUMENTATION file?

[1234-ad]

Hi @glowcloud,

Thanks for the feedback! I've removed the FIX_DOCUMENTATION.md file as requested. The PR now contains only the essential .npmignore fix.

The change is ready for review.

[glowcloud]

Thanks for the quick update @1234-ad! LGTM now!

[swagger-bot]

🎉 This PR is included in version 5.29.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[hernandez1234anna-dotcom]

Fix for Issue #10574: Include oauth2-redirect.js in npm package

Problem

The oauth2-redirect.js file was missing from the npm package distribution, causing OAuth2 authentication to fail when using the npm package. The file exists in the repository and is referenced by oauth2-redirect.html, but wasn't being packaged.

Root Cause

The .npmignore file uses a whitelist approach (excluding everything with * and then including specific files with !). It included !dist/oauth2-redirect.html but was missing !dist/oauth2-redirect.js.

Solution

Added !dist/oauth2-redirect.js to the .npmignore file whitelist.

Changes Made

• .npmignore: Added !dist/oauth2-redirect.js to ensure the file is included in npm packages

Verification

After this fix, npm pack swagger-ui will include both:

• ✅ dist/oauth2-redirect.html (already included)
• ✅ dist/oauth2-redirect.js (now included)

Impact

• ✅ Fixes OAuth2 authentication when using npm package
• ✅ No breaking changes - purely additive
• ✅ Maintains backward compatibility
• ✅ Simple, targeted fix with minimal risk

Testing

The fix can be verified by:

1. Running npm pack swagger-ui
2. Checking that oauth2-redirect.js is now included in the package contents
3. Confirming OAuth2 flows work properly with the npm package

This is a critical fix for OAuth2 functionality that was broken due to missing file packaging.

Fixes #10574