@holz/pattern-filter 0.8.3-rc.154 → 0.8.3-rc.155

package/dist/{src/pattern-filter.d.ts → holz-pattern-filter.d.ts}

@@ -1,24 +1,27 @@
-import { LogProcessor } from '@holz/core';
-/**
- * Only forwards logs who's origin matches the given pattern. It works the
- * same as the popular `debug` module.
- *
- * Patterns allow wildcards and negation. For example, the pattern `my-app*`
- * will match all logs with the origin `my-app` or `my-app:foo` or
- * `my-app:foo:bar`. The pattern `*, -my-app` will match all logs except those
- * with the origin `my-app`.
- *
- * @example
- * createPatternFilter({
- *   pattern: 'my-app*, -spammy:library',
- *   processor: backend,
- * })
- */
-export declare const createPatternFilter: ({ processor, pattern, }: Config) => LogProcessor;
-interface Config {
-    /** A set of patterns to test against `log.origin`. */
-    pattern: string;
-    /** Where to send logs if they pass the filter. */
-    processor: LogProcessor;
-}
-export {};
+import { LogProcessor } from '@holz/core';
+
+declare interface Config {
+    /** A set of patterns to test against `log.origin`. */
+    pattern: string;
+    /** Where to send logs if they pass the filter. */
+    processor: LogProcessor;
+}
+
+/**
+ * Only forwards logs who's origin matches the given pattern. It works the
+ * same as the popular `debug` module.
+ *
+ * Patterns allow wildcards and negation. For example, the pattern `my-app*`
+ * will match all logs with the origin `my-app` or `my-app:foo` or
+ * `my-app:foo:bar`. The pattern `*, -my-app` will match all logs except those
+ * with the origin `my-app`.
+ *
+ * @example
+ * createPatternFilter({
+ *   pattern: 'my-app*, -spammy:library',
+ *   processor: backend,
+ * })
+ */
+export declare const createPatternFilter: ({ processor, pattern, }: Config) => LogProcessor;
+
+export { }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@holz/pattern-filter",
-  "version": "0.8.3-rc.154+3f5148e",
+  "version": "0.8.3-rc.155+ca9302f",
   "description": "Only print log messages that match a pattern",
   "type": "module",
   "repository": {
@@ -40,7 +40,8 @@
     "@holz/core": "^0.8.0"
   },
   "devDependencies": {
-    "@holz/core": "^0.8.3-rc.154+3f5148e",
+    "@holz/core": "^0.8.3-rc.155+ca9302f",
+    "@microsoft/api-extractor": "^7.58.8",
     "@vitest/coverage-v8": "^4.0.0",
     "typescript": "^6.0.0",
     "vite": "^8.0.0",
@@ -48,5 +49,5 @@
     "vite-tsconfig-paths": "^6.0.0",
     "vitest": "^4.0.0"
   },
-  "gitHead": "3f5148eb94bb1d7200d4b4993c95ea30db76b0c4"
+  "gitHead": "ca9302f8b1709bb57058eb0dc73af0ed2021ddfd"
 }

package/dist/src/__tests__/pattern-filter.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/src/__tests__/string-match.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/src/index.d.ts

@@ -1 +0,0 @@
-export { createPatternFilter } from './pattern-filter';

package/dist/src/string-match.d.ts

@@ -1,16 +0,0 @@
-/**
- * Parse a string of multiple patterns into a set of regular expressions. We
- * use a pattern string (instead of regexes) because it's easier to persist in
- * storage or specify through a CLI.
- *
- * Special thanks to `debug-js` for the inspiration. I read their code as
- * a guide for this implementation.
- */
-export declare const parse: (input: string) => PatternFilters;
-/** Detect if a string matches a set of patterns. */
-export declare const matches: (filters: PatternFilters, input: string) => boolean;
-interface PatternFilters {
-    include: Array<RegExp>;
-    exclude: Array<RegExp>;
-}
-export {};