@absolutejs/absolute 0.19.0-beta.957 → 0.19.0-beta.958
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/angular/components/core/streamingSlotRegistrar.js +1 -1
- package/dist/angular/components/core/streamingSlotRegistry.js +2 -2
- package/dist/build.js +2011 -763
- package/dist/build.js.map +11 -4
- package/dist/index.js +16076 -15944
- package/dist/index.js.map +11 -10
- package/dist/src/build/scanRouteRegistrations.d.ts +16 -0
- package/dist/src/core/prepare.d.ts +2 -2
- package/dist/src/utils/generateSitemap.d.ts +7 -0
- package/package.json +1 -1
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
export type ExtractedRoute = {
|
|
2
|
+
/** Uppercase HTTP method, matching Elysia's runtime `route.method`. */
|
|
3
|
+
method: string;
|
|
4
|
+
/** Path argument literal — including leading slash, no host. */
|
|
5
|
+
path: string;
|
|
6
|
+
/** Verbatim source of the full `.method(...)` CallExpression. Used
|
|
7
|
+
* downstream as a stand-in for the runtime handler so the existing
|
|
8
|
+
* `isPageHandler` / `extractSitemapMetadata` substring checks work
|
|
9
|
+
* unchanged against AST-discovered routes. */
|
|
10
|
+
handlerSource: string;
|
|
11
|
+
};
|
|
12
|
+
/** Walk every TypeScript source file under `projectRoot` and return the
|
|
13
|
+
* Elysia route registrations found. Skip-dirs (`node_modules`, `dist`,
|
|
14
|
+
* `build`, framework build caches, dotfile dirs) are excluded. Duplicate
|
|
15
|
+
* `method + path` pairs are deduplicated, last definition wins. */
|
|
16
|
+
export declare const scanRouteRegistrations: (projectRoot: string) => ExtractedRoute[];
|
|
@@ -43,7 +43,7 @@ export declare const prepare: (configOrPath?: string) => Promise<{
|
|
|
43
43
|
response: {
|
|
44
44
|
200: Response;
|
|
45
45
|
};
|
|
46
|
-
}, (((
|
|
46
|
+
}, ((({
|
|
47
47
|
".well-known": {
|
|
48
48
|
appspecific: {
|
|
49
49
|
"com.chrome.devtools.json": {
|
|
@@ -226,7 +226,7 @@ export declare const prepare: (configOrPath?: string) => Promise<{
|
|
|
226
226
|
};
|
|
227
227
|
};
|
|
228
228
|
};
|
|
229
|
-
}) & {}) & {}
|
|
229
|
+
}) & {}) & {}, {
|
|
230
230
|
derive: {};
|
|
231
231
|
resolve: {};
|
|
232
232
|
schema: {};
|
|
@@ -2,7 +2,14 @@ import type { SitemapConfig } from '../../types/sitemap';
|
|
|
2
2
|
type AppRoute = {
|
|
3
3
|
method: string;
|
|
4
4
|
path: string;
|
|
5
|
+
/** Runtime handler — `.toString()` is read to detect page handlers. */
|
|
5
6
|
handler?: unknown;
|
|
7
|
+
/** Pre-extracted handler source. Set by the build-time route scanner
|
|
8
|
+
* in place of `handler` so the page-handler heuristic and the
|
|
9
|
+
* `sitemap: { ... }` metadata regex work without instantiating any
|
|
10
|
+
* function. Either field is sufficient; if both are set,
|
|
11
|
+
* `handlerSource` wins. */
|
|
12
|
+
handlerSource?: string;
|
|
6
13
|
};
|
|
7
14
|
export type SitemapPipelineConfig = {
|
|
8
15
|
angularDirectory?: string;
|
package/package.json
CHANGED