minor fixes

v1.3.2

1.3.2

v1.3.1 - fix Token Storage Priority

Fixed

• Token Storage Priority - Storage is now checked before calling tokenProvider
  • Previously: When tokenProvider was configured, it was always called first, even if valid tokens existed in storage
  • Now: Storage is ALWAYS checked first, tokenProvider only called when storage is empty
  • This prevents unnecessary provider calls on subsequent runs after initial authentication
  • Tokens from tokenProvider are still saved to storage for future use
  • Results in much faster startup times when tokens are already cached

v1.3.0 - fix token management

Added

• Automatic Token Refresh & Retry Mechanism (inspired by fs-box-sync)

  • Added withRetry() wrapper for all API operations - automatically retries on 401 errors
  • Added invalidateAndRefresh() for smart token recovery (refresh token → token provider fallback)
  • Added enhanceError() for user-friendly error messages (401, 404, 403, 409, 500+ status codes)
  • Added isRetrying flag to prevent infinite retry loops
  • All 23 service methods across 4 files now use checkToken() + withRetry() + getAxon() pattern
  • Zero legacy try-catch + handleApiError patterns remaining

• Centralized SSL Configuration

  • Added getAxon() helper method - returns Axon.dev() when allowInsecure: true, Axon.new() otherwise
  • allowInsecure option now applies to ALL API calls (auth + services), not just token endpoints
  • Created comprehensive test suite for allowInsecure option (tests/allow-insecure.test.ts)

Fixed

• Token Storage with Token Provider - Tokens obtained from tokenProvider are now saved to storage

  • Previously: Storage was skipped when tokenProvider was configured, causing provider to be called on every execution
  • Now: Tokens are cached to storage even with tokenProvider, reducing unnecessary provider calls
  • Matches fs-box-sync behavior: only skips storage for access-token-only mode
  • Storage now happens after both refreshAccessToken() and forgeRefreshToken()

• SSL Verification with allowInsecure - Setting allowInsecure: true now works correctly

  • Previously: Only applied to auth endpoints, service API calls still used secure SSL
  • Now: All HTTP requests (auth + services) respect the allowInsecure setting
  • Uses centralized getAxon() method for consistent behavior across all 23 service methods
  • Removed all legacy Axon.new() direct calls from service files

• 401 Error Handling - API calls now automatically recover from authentication failures

  • Previously: 401 errors caused immediate failures with generic error messages
  • Now: Automatic token refresh + single retry on 401 errors
  • Fallback chain: refresh token → token provider → helpful error message
  • Prevents cascading failures and improves user experience

v1.2.0 - AWS SDK-Style Global Instance API

Added

• AWS SDK-Style Global Instance API
  • Added lazy-loaded service getters: Azure.outlook, Azure.teams, Azure.calendar, Azure.sharePoint
  • Services are now accessible directly after calling Azure.config() - no manual instantiation needed
  • Singleton pattern: same instance returned on multiple accesses
  • Lazy initialization: services only created when first accessed
  • Azure.reset() now clears all service instances for clean state

Changed

• ⚠️ BREAKING: Dropped Node.js 18 support
  • Minimum Node.js version is now 20.0.0
  • Node.js 18 reached End-of-Life on April 30, 2025
  • This change enables better compatibility with modern dependencies
• ⚠️ API Improvement: Simplified service access pattern
  • Before: Azure.config({...}); const outlook = new Outlook(); await outlook.sendMail({...});
  • After: Azure.config({...}); await Azure.outlook.sendMail({...});
  • No more manual service instantiation required
  • Global config is automatically applied to all services
  • Calling Azure.config() resets all service instances to pick up new configuration
  • Old pattern (new Outlook()) still works for advanced use cases

Documentation

• Complete README rewrite to showcase new API pattern
• Updated all examples to use Azure.service syntax
• Added comprehensive vitest test suite for new API (tests/azure-api.test.ts)
• Updated Three-Tier User System examples
• Updated Service Usage Patterns section
• Clarified FAQ and troubleshooting for new API

Migration Guide

Old Pattern (Still Supported):

import { Outlook, Teams } from 'ms-graph-devtools';

const outlook = new Outlook({
  clientId: "...",
  clientSecret: "...",
  tenantId: "...",
  refreshToken: "..."
});

await outlook.sendMail({...});

New Pattern (Recommended):

import Azure from 'ms-graph-devtools';

// Configure once
Azure.config({
  clientId: "...",
  clientSecret: "...",
  tenantId: "...",
  refreshToken: "..."
});

// Export for use across your app
export default Azure;

// Use services directly - no instantiation needed!
await Azure.outlook.sendMail({...});
await Azure.teams.postMessage({...});
await Azure.calendar.getCalendars();
await Azure.sharePoint.getLists();

Benefits:

• ✅ Configure once, use everywhere
• ✅ No redundant init() or instantiation
• ✅ Clean, AWS SDK-like API
• ✅ Better discoverability (IDE autocomplete shows all services)
• ✅ Still tree-shakable (unused services won't be bundled)

v1.1.1 - Updated tokenProvider signature

Changed

• ⚠️ BREAKING: Updated tokenProvider signature
  • tokenProvider now receives the OAuth callback URL as a parameter
  • Old: tokenProvider?: () => Promise<string> | string
  • New: tokenProvider?: (callback: string) => Promise<string> | string
  • The callback URL contains all OAuth parameters (tenantId, clientId, scopes, redirectUri)
  • tokenProvider should return the authorization code (not refresh token)
  • Library now handles the code-to-token exchange internally via forgeRefreshToken()

Added

• OAuth Authorization Code Flow: New forgeRefreshToken() method
  • Constructs OAuth authorization URL with configured parameters
  • Exchanges authorization code for access_token, refresh_token, and expires_in
  • Enables full Playwright integration for automated authentication

Migration Guide

If you're using tokenProvider, update your implementation:

Before:

const outlook = new Outlook({
  tokenProvider: async () => {
    // Return refresh token from vault
    return await fetchFromVault('azure-refresh-token');
  }
});

After:

const outlook = new Outlook({
  tokenProvider: async (callback: string) => {
    // callback contains the OAuth authorization URL
    // Use Playwright to navigate, login, and extract the code
    const code = await Playwright.getAzureCode(callback);
    return code;
  }
});

v1.1.0 - Converted package to pure ESM

Added

• ESLint Configuration: Full ESLint setup with TypeScript support
  • Modern flat config format (eslint.config.js)
  • TypeScript-specific linting rules
  • Prettier integration to prevent conflicts
  • Special rules for test files (allows any for mocking)
  • Excludes examples directory from linting
  • npm scripts: npm run lint and npm run lint:fix

Changed

• ⚠️ BREAKING: Converted package to pure ESM (ES Modules)

  • Added "type": "module" to package.json
  • Updated TypeScript configuration to output ESNext modules
  • Changed module from "commonjs" to "ESNext" in tsconfig.json
  • Changed moduleResolution from "node" to "bundler" in tsconfig.json
  • All imports now require .js extensions in distributed code
  • Removed CommonJS exports (no more require() support)
  • Updated index.js and index.d.ts to use ESM syntax
  • Package now only supports ESM consumers (Node.js 14+ with ESM)

• Code Quality Improvements:

  • Replaced any types with proper type annotations where possible
  • Added AxonError type imports from axios-fluent for better error handling
  • Removed unused imports and variables throughout codebase
  • Fixed unnecessary try-catch wrappers
  • Fixed unnecessary escape characters in template literals
  • Improved type safety in error handling using NodeJS.ErrnoException
  • All source files now pass strict ESLint checks

Migration Guide

If you're upgrading from a CommonJS version:

Before (CommonJS):

const { Outlook, Teams } = require('ms-graph-devtools');

After (ESM):

import { Outlook, Teams } from 'ms-graph-devtools';

For TypeScript users:

• Ensure your tsconfig.json has "module": "ESNext" or "NodeNext"
• Ensure your package.json has "type": "module"

For Node.js users:

• Requires Node.js 14+ with ESM support
• Add "type": "module" to your package.json, OR
• Use .mjs file extensions for your entry points