fix: include exports for non-node environments

[danbillson]

Related to issue: #117

Includes additional exports for non-node environments, allowing the runtime to pick up the edge build, which has a replacement implementation for node:crypto unavailable in other runtimes.

Usage with nextjs on cloudflare

As we've seen a couple issue with @paddle/paddle-node-sdk and nextjs on cloudflare, here is a usage guide:

Import the Paddle class from @paddle/paddle-node-sdk in the API route and create the instance in the route handler

// app/api/webhook/route.ts

export const runtime = "edge";

import {
  Environment,
  LogLevel,
  Paddle,
  PaddleOptions,
} from "@paddle/paddle-node-sdk";
import { NextRequest } from "next/server";

const paddleOptions: PaddleOptions = {
  environment:
    (process.env.NEXT_PUBLIC_PADDLE_ENV as Environment) ?? Environment.sandbox,
  logLevel: LogLevel.error,
};

export async function GET(request: NextRequest) {
  const paddle = new Paddle(process.env.PADDLE_API_KEY!, paddleOptions);

  return Response.json({ paddle, success: true });
}

Note: This will not work if you create a separate utility outside of the API route i.e. a getPaddleInstance utility as it will try and use the node runtime