@vercube/scan 1.1.7 → 1.2.1
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/index.d.mts +2 -2
- package/dist/index.mjs +2 -2
- package/package.json +2 -2
package/dist/index.d.mts
CHANGED
|
@@ -155,7 +155,7 @@ declare function extractRoutes(code: string): RouteInfo[];
|
|
|
155
155
|
* regardless of whether it declares HTTP method routes.
|
|
156
156
|
*
|
|
157
157
|
* Unlike {@link extractRoutes} (which emits one entry per HTTP route method),
|
|
158
|
-
* this returns one entry per controller class
|
|
158
|
+
* this returns one entry per controller class - so controllers that only carry
|
|
159
159
|
* non-HTTP handlers (e.g. WebSocket `@Message` methods) are still discovered for
|
|
160
160
|
* binding into the DI container.
|
|
161
161
|
*
|
|
@@ -252,7 +252,7 @@ interface ScanSourceOptions {
|
|
|
252
252
|
* once.
|
|
253
253
|
*
|
|
254
254
|
* Unlike {@link scanProject}, this does not assume the Nitro convention of
|
|
255
|
-
* dedicated `api`/`routes`/`services` subdirectories
|
|
255
|
+
* dedicated `api`/`routes`/`services` subdirectories - decorated classes are
|
|
256
256
|
* discovered wherever they live in the tree, which matches how Vercube apps are
|
|
257
257
|
* typically organised. **Every** `@Controller` class is returned for binding
|
|
258
258
|
* (not just those with HTTP routes), so WebSocket-only controllers are bound
|
package/dist/index.mjs
CHANGED
|
@@ -210,7 +210,7 @@ function extractRoutes(code) {
|
|
|
210
210
|
* regardless of whether it declares HTTP method routes.
|
|
211
211
|
*
|
|
212
212
|
* Unlike {@link extractRoutes} (which emits one entry per HTTP route method),
|
|
213
|
-
* this returns one entry per controller class
|
|
213
|
+
* this returns one entry per controller class - so controllers that only carry
|
|
214
214
|
* non-HTTP handlers (e.g. WebSocket `@Message` methods) are still discovered for
|
|
215
215
|
* binding into the DI container.
|
|
216
216
|
*
|
|
@@ -462,7 +462,7 @@ async function scanProject(options) {
|
|
|
462
462
|
* once.
|
|
463
463
|
*
|
|
464
464
|
* Unlike {@link scanProject}, this does not assume the Nitro convention of
|
|
465
|
-
* dedicated `api`/`routes`/`services` subdirectories
|
|
465
|
+
* dedicated `api`/`routes`/`services` subdirectories - decorated classes are
|
|
466
466
|
* discovered wherever they live in the tree, which matches how Vercube apps are
|
|
467
467
|
* typically organised. **Every** `@Controller` class is returned for binding
|
|
468
468
|
* (not just those with HTTP routes), so WebSocket-only controllers are bound
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@vercube/scan",
|
|
3
|
-
"version": "1.1
|
|
3
|
+
"version": "1.2.1",
|
|
4
4
|
"description": "Source scanning and AST extraction utilities for the Vercube framework",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|
|
@@ -28,7 +28,7 @@
|
|
|
28
28
|
"framework"
|
|
29
29
|
],
|
|
30
30
|
"dependencies": {
|
|
31
|
-
"oxc-parser": "0.
|
|
31
|
+
"oxc-parser": "0.144.0",
|
|
32
32
|
"pathe": "2.0.3",
|
|
33
33
|
"tinyglobby": "0.2.17"
|
|
34
34
|
},
|