feat: add named exports

Exposing the various types and classes for programatical usage
with a shortcut for the complexity calculation. This should
give a decent support for functional or object-oriented support
while keeping the changes low.

refs: simonrenoult#8

Author: adaliszk

README.md

@@ -26,6 +26,25 @@ Note: `code-complexity` currently measures complexity using either:
 $ npx code-complexity <path-to-git-directory or URL> [options]
 ```
 
+or
+
+```javascript
+// CommonJS
+const complexity = require("code-complexity")
+const results = await complexity.compute({
+  target: "some/file/path"
+})
+```
+
+```typescript
+// ES Modules
+import { analyize } from "code-complexity";
+
+const results = await analyize({
+  target: "some/file/path"
+})
+```
+
 ## Help
 
 ```text

src/lib/index.ts

@@ -1,3 +1,21 @@
 import Statistics from "./statistics/statistics";
+import Churns from "./churn/churns";
+import Complexities from "./complexity/complexities";
 
+// Expose shared type interfaces
+export * from "./types";
+
+// For CommonJS support: require("code-complexity")
 export default Statistics;
+
+// For ESM functional-style support: import { analyize } from "code-complexity";
+export const analyize = Statistics.compute;
+export const analyise = Statistics.compute;
+
+// For ESM object-style: `import { Statistics } from "code-complexity"`
+export {
+  Statistics,
+  // Expose these as they are dependencies for Statistics
+  Churns,
+  Complexities,
+};