Name the export for consistent use across ESM and CJS with correct typing

Author: steverep

README.md

@@ -20,13 +20,15 @@ Any `devTool` (source maps) option used in Webpack is supported. This includes "
 Install the package from NPM and require or import it for your Webpack configuration:
 
 ```js
-const TransformAsyncModulesPlugin = require("transform-async-modules-webpack-plugin");
+const {
+  TransformAsyncModulesPlugin,
+} = require("transform-async-modules-webpack-plugin");
 ```
 
 or
 
 ```js
-import TransformAsyncModulesPlugin from "transform-async-modules-webpack-plugin";
+import { TransformAsyncModulesPlugin } from "transform-async-modules-webpack-plugin";
 ```
 
 Then add an instance to the plugins array:

package.json

@@ -1,7 +1,7 @@
 {
   "name": "transform-async-modules-webpack-plugin",
   "description": "A Webpack plugin to transpile async module output using Babel. Allows transpiling top level await to ES5.",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "license": "MIT",
   "homepage": "https://github.com/steverep/transform-async-modules-webpack-plugin",
   "keywords": [

src/index.cts

@@ -10,7 +10,7 @@ export type TransformAsyncModulesPluginOptions = Pick<
 
 const PLUGIN_NAME = "TransformAsyncModulesPlugin " as const;
 
-export default class TransformAsyncModulesPlugin {
+export class TransformAsyncModulesPlugin {
   babelOptions: TransformOptions = {};
 
   constructor(options: TransformAsyncModulesPluginOptions = {}) {