@aburi/effects-prisma 0.4.0 → 0.4.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 +44 -196
- package/dist/index.mjs +1 -1
- package/package.json +5 -4
package/dist/index.d.mts
CHANGED
|
@@ -4,112 +4,44 @@ import { CallCandidate, ClassifyContext, Confidence, EffectClassification, Effec
|
|
|
4
4
|
/**
|
|
5
5
|
* Classify a CallCandidate against Prisma Client conventions.
|
|
6
6
|
*
|
|
7
|
-
*
|
|
8
|
-
*
|
|
9
|
-
*
|
|
10
|
-
*
|
|
11
|
-
*
|
|
12
|
-
*
|
|
13
|
-
*
|
|
14
|
-
*
|
|
15
|
-
*
|
|
16
|
-
*
|
|
17
|
-
*
|
|
18
|
-
*
|
|
19
|
-
*
|
|
20
|
-
*
|
|
21
|
-
*
|
|
22
|
-
* call is not classified at all.
|
|
23
|
-
* 4. Malformed targets (empty string, adjacent / leading / trailing dots) throw — the
|
|
24
|
-
* language plugin's contract is a normalized non-empty callee, so a violation
|
|
25
|
-
* here is an upstream bug we surface loudly instead of silently miscategorizing.
|
|
26
|
-
*
|
|
27
|
-
* **The import gate is not a receiver check.** It answers "does this file use Prisma",
|
|
28
|
-
* which a file is free to answer yes to while most of its calls belong to something else:
|
|
29
|
-
* `this.cache.items.delete(key)` is a `Map`, `session.user.update(fields)` is an object,
|
|
30
|
-
* and both have three segments and a delegate verb. Step 3 is what keeps those from being
|
|
31
|
-
* recorded as `db.write` at the tier a hand-annotated effect gets — a claim that
|
|
32
|
-
* would then propagate through the call graph and into the diff. Where the receiver names
|
|
33
|
-
* the client, the classification still lands at `high`; where it does not, the effect is
|
|
34
|
-
* still emitted but at `medium`, because a syntactic classifier cannot tell a client under
|
|
35
|
-
* a house naming convention apart from an unrelated object of the same shape, and silently
|
|
36
|
-
* dropping the first is as wrong as confidently claiming the second.
|
|
37
|
-
*
|
|
38
|
-
* The function is a pure lookup — no I/O, no state, no async — matching the per-call
|
|
39
|
-
* timeout budget the core enforces (effect-plugin.md §5.1.1).
|
|
7
|
+
* Two shapes are accepted once the file imports a Prisma Client module (`hasPrismaImport`):
|
|
8
|
+
* - `<...>.<model>.<verb>` (3+ segments) — a model delegate call. The client segment is
|
|
9
|
+
* what separates it from two-segment collisions such as Express `router.create(...)`.
|
|
10
|
+
* - `<...>.$transaction` (2+ segments) — the transaction API on the client itself.
|
|
11
|
+
*
|
|
12
|
+
* The import gate is not a receiver check: `this.cache.items.delete(key)` is a `Map` and
|
|
13
|
+
* `session.user.update(fields)` an object, both three segments with a delegate verb in a
|
|
14
|
+
* file that also uses Prisma. A literal first argument rules a call out — no Prisma method
|
|
15
|
+
* takes one — and the receiver plus argument count decide the tier, downgrading rather
|
|
16
|
+
* than dropping (`receiverConfidence`). A model addressed through brackets arrives as
|
|
17
|
+
* `<computed>` and supplies the third segment without a model, so there the receiver must
|
|
18
|
+
* name a client outright.
|
|
19
|
+
*
|
|
20
|
+
* Throws on a malformed target (`assertNonEmptySegments`): an upstream contract violation,
|
|
21
|
+
* not a classification decision. Pure with respect to plugin state (effect-plugin.md).
|
|
40
22
|
*/
|
|
41
23
|
declare function classifyPrismaCall(call: CallCandidate, ctx: ClassifyContext): EffectClassification | null;
|
|
42
24
|
//#endregion
|
|
43
25
|
//#region src/constants.d.ts
|
|
44
|
-
/**
|
|
45
|
-
* Package-relative plugin name. Doubles as the prefix of every thrown message, so a caught
|
|
46
|
-
* exception names the plugin that rejected the input. `manifest.ts` declares the same
|
|
47
|
-
* string as `name`.
|
|
48
|
-
*/
|
|
26
|
+
/** Plugin name: the manifest's `name` and the prefix of every thrown message. */
|
|
49
27
|
declare const EFFECTS_PRISMA_PLUGIN_NAME: "effects-prisma";
|
|
50
|
-
/**
|
|
51
|
-
* Shared derivedBy namespace. `manifest.ts` imports this same const for its
|
|
52
|
-
* `derivedByPrefixes` entry, so the classifier's tag builder and the registry
|
|
53
|
-
* declaration cannot drift.
|
|
54
|
-
*/
|
|
28
|
+
/** derivedBy namespace shared by the classifier's tag builder and the manifest. */
|
|
55
29
|
declare const EFFECTS_PRISMA_DERIVED_BY_PREFIX: "effects-plugin:prisma";
|
|
56
30
|
//#endregion
|
|
57
31
|
//#region src/imports.d.ts
|
|
58
|
-
/**
|
|
59
|
-
* True when the file's import list contains any recognized Prisma Client module. An
|
|
60
|
-
* empty source string on an ImportEdge is rejected by the shared guard: the language
|
|
61
|
-
* plugin's contract is to emit normalized non-empty specifiers, and treating `""` as
|
|
62
|
-
* unmatched would silently hide upstream bugs.
|
|
63
|
-
*
|
|
64
|
-
* `filePath` is required and threaded into any thrown error message so a caught
|
|
65
|
-
* exception in production tooling (CI logs, error reporters) points directly at the
|
|
66
|
-
* offending source file rather than a bare "empty source" string.
|
|
67
|
-
*/
|
|
32
|
+
/** True when the file imports a Prisma Client module; see `hasMatchingImport`. */
|
|
68
33
|
declare function hasPrismaImport(imports: readonly ImportEdge[], filePath: string): boolean;
|
|
69
34
|
//#endregion
|
|
70
35
|
//#region src/manifest.d.ts
|
|
71
|
-
/**
|
|
72
|
-
|
|
73
|
-
* every literal narrow so downstream registry checks see the exact shape.
|
|
74
|
-
*
|
|
75
|
-
* The plugin returns core-owned effect ids (`db.read` / `db.write` / `db.transaction`)
|
|
76
|
-
* from `classify()`; per extension-vocab.md §5.1 core vocab lives in the reserved
|
|
77
|
-
* namespace and MUST NOT appear in a plugin's `provides.effects`. The plugin's own
|
|
78
|
-
* `x-prisma:*` namespace currently has no bindings — model-specific effects would sit there
|
|
79
|
-
* once introduced. `derivedByPrefixes` shares its literal with the classifier's tag
|
|
80
|
-
* builder so both stay in lockstep across edits.
|
|
81
|
-
*/
|
|
82
|
-
declare const effectsPrismaManifest: {
|
|
83
|
-
readonly $schema: "https://aburi.kage1020.com/schema/aburi.plugin.v1.json";
|
|
84
|
-
readonly name: "effects-prisma";
|
|
85
|
-
readonly version: "0.0.0";
|
|
86
|
-
readonly type: "effects";
|
|
87
|
-
readonly engines: {
|
|
88
|
-
readonly aburi: "*";
|
|
89
|
-
};
|
|
90
|
-
readonly provides: {
|
|
91
|
-
readonly effects: [];
|
|
92
|
-
readonly effectPrefixes: [];
|
|
93
|
-
readonly extKinds: [];
|
|
94
|
-
readonly extKindPrefixes: [];
|
|
95
|
-
readonly derivedByPrefixes: ["effects-plugin:prisma"];
|
|
96
|
-
readonly frameworks: [];
|
|
97
|
-
};
|
|
98
|
-
};
|
|
36
|
+
/** See `defineEffectsManifest` for why `provides` claims no vocabulary of its own. */
|
|
37
|
+
declare const effectsPrismaManifest: import("@aburi/plugin-registry/plugin-input").EffectsPluginManifest<"effects-prisma", "effects-plugin:prisma">;
|
|
99
38
|
//#endregion
|
|
100
39
|
//#region src/methods.d.ts
|
|
101
40
|
/**
|
|
102
|
-
* Prisma model delegate method vocabulary.
|
|
103
|
-
*
|
|
104
|
-
*
|
|
105
|
-
*
|
|
106
|
-
* place. Extending as Prisma ships new delegate methods keeps the classifier honest
|
|
107
|
-
* without a code rewrite.
|
|
108
|
-
*
|
|
109
|
-
* Only methods that map cleanly onto core `db.read` / `db.write` vocabulary are listed.
|
|
110
|
-
* Delegate helpers whose semantics do not match (metadata accessors, raw SQL escapes,
|
|
111
|
-
* connection lifecycle) stay out — the plugin returns `null` for them so downstream
|
|
112
|
-
* effect plugins get a chance.
|
|
41
|
+
* Prisma model delegate method vocabulary. Each `_LIST` is the single source of truth for
|
|
42
|
+
* its union type and runtime `Set`. Only methods that map onto core `db.read` / `db.write`
|
|
43
|
+
* are listed; metadata accessors, raw SQL escapes and connection lifecycle stay out, so the
|
|
44
|
+
* plugin returns `null` for them and downstream effect plugins get a chance.
|
|
113
45
|
*/
|
|
114
46
|
declare const PRISMA_READ_METHODS_LIST: readonly ["findUnique", "findUniqueOrThrow", "findFirst", "findFirstOrThrow", "findMany", "count", "aggregate", "groupBy"];
|
|
115
47
|
declare const PRISMA_WRITE_METHODS_LIST: readonly ["create", "createMany", "createManyAndReturn", "update", "updateMany", "updateManyAndReturn", "upsert", "delete", "deleteMany"];
|
|
@@ -126,84 +58,31 @@ declare function isPrismaTransactionMethod(name: string): name is PrismaTransact
|
|
|
126
58
|
//#endregion
|
|
127
59
|
//#region src/plugin.d.ts
|
|
128
60
|
/**
|
|
129
|
-
* Prisma effect plugin
|
|
130
|
-
* `
|
|
131
|
-
*
|
|
132
|
-
*
|
|
133
|
-
* `init` and `classify` are both pure with respect to plugin state — no lazy resources,
|
|
134
|
-
* no per-run caches — so repeated invocations against the same CallCandidate produce
|
|
135
|
-
* identical results. This matches the per-call timeout contract in
|
|
136
|
-
* effect-plugin.md §5.1.1 and the "pure classifier" recommendation in §11.1.
|
|
61
|
+
* Prisma effect plugin: maps `prisma.<model>.<verb>` and `prisma.$transaction` call
|
|
62
|
+
* expressions onto the core `db.read` / `db.write` / `db.transaction` vocabulary. `classify`
|
|
63
|
+
* is pure (effect-plugin.md) and throws on a malformed CallCandidate — an
|
|
64
|
+
* upstream contract violation, surfaced rather than swallowed.
|
|
137
65
|
*/
|
|
138
66
|
declare class PrismaEffectsPlugin implements EffectPlugin {
|
|
139
|
-
readonly manifest:
|
|
140
|
-
readonly $schema: "https://aburi.kage1020.com/schema/aburi.plugin.v1.json";
|
|
141
|
-
readonly name: "effects-prisma";
|
|
142
|
-
readonly version: "0.0.0";
|
|
143
|
-
readonly type: "effects";
|
|
144
|
-
readonly engines: {
|
|
145
|
-
readonly aburi: "*";
|
|
146
|
-
};
|
|
147
|
-
readonly provides: {
|
|
148
|
-
readonly effects: [];
|
|
149
|
-
readonly effectPrefixes: [];
|
|
150
|
-
readonly extKinds: [];
|
|
151
|
-
readonly extKindPrefixes: [];
|
|
152
|
-
readonly derivedByPrefixes: ["effects-plugin:prisma"];
|
|
153
|
-
readonly frameworks: [];
|
|
154
|
-
};
|
|
155
|
-
};
|
|
67
|
+
readonly manifest: import("@aburi/plugin-registry/plugin-input").EffectsPluginManifest<"effects-prisma", "effects-plugin:prisma">;
|
|
156
68
|
init(_ctx: PluginContext): Promise<void>;
|
|
157
69
|
classify(call: CallCandidate, ctx: ClassifyContext): EffectClassification | null;
|
|
158
70
|
}
|
|
159
|
-
/**
|
|
160
|
-
* Ready-to-register instance. Callers pass this to `@aburi/plugin-registry` or a scan
|
|
161
|
-
* pipeline. The type annotation is omitted deliberately: `class implements EffectPlugin`
|
|
162
|
-
* already enforces the structural contract, and inferring the narrow class type keeps
|
|
163
|
-
* the manifest literals (`readonly ["effects-plugin:prisma"]`, `"effects-prisma"`)
|
|
164
|
-
* visible to consumers that want to compare against them without a separate manifest
|
|
165
|
-
* import.
|
|
166
|
-
*/
|
|
71
|
+
/** Ready-to-register instance; left unannotated so the manifest literals stay visible. */
|
|
167
72
|
declare const prismaEffectsPlugin: PrismaEffectsPlugin;
|
|
168
73
|
//#endregion
|
|
169
74
|
//#region src/receivers.d.ts
|
|
170
75
|
/**
|
|
171
|
-
* The words a Prisma Client binding is spelled with.
|
|
172
|
-
*
|
|
173
|
-
*
|
|
174
|
-
*
|
|
175
|
-
*
|
|
176
|
-
*
|
|
177
|
-
*
|
|
178
|
-
*
|
|
179
|
-
*
|
|
180
|
-
*
|
|
181
|
-
* `dbClient` and `prismaRo` all count, while `cache`, `router`, `items` and `store` do not.
|
|
182
|
-
* That is the whole point: `delete`, `create` and `update` are shared vocabulary across
|
|
183
|
-
* `Map`, `Set`, the DOM and every HTTP router, and `this.<x>.<y>.delete(...)` is everyday
|
|
184
|
-
* TypeScript, so the method name plus a file-level import gate is not evidence that the
|
|
185
|
-
* receiver is a database client.
|
|
186
|
-
*
|
|
187
|
-
* `tx` / `trx` are here because the interactive-transaction callback rebinds the client
|
|
188
|
-
* under its own parameter name — `prisma.$transaction(async (tx) => tx.user.create(...))` —
|
|
189
|
-
* and that call is as much a write as the one outside it.
|
|
190
|
-
*
|
|
191
|
-
* **What is deliberately not here.** A word only earns a place if it separates a database
|
|
192
|
-
* client from everything else that shares Prisma's verbs:
|
|
193
|
-
*
|
|
194
|
-
* - `client` matches `apiClient`, `httpClient`, `redisClient`, `sdkClient`. A resource
|
|
195
|
-
* SDK's `<client>.<resource>.<verb>` is spelled exactly like a Prisma delegate, so
|
|
196
|
-
* `apiClient.users.update(payload)` would land at the tier a hand-annotated effect gets
|
|
197
|
-
* — the bug class this module exists to close. `prismaClient`, `dbClient` and `_prisma`
|
|
198
|
-
* match on `prisma` or `db` regardless; a bare `client.user.create()` is all the entry
|
|
199
|
-
* would have bought.
|
|
200
|
-
* - `transaction` matches the domain nouns `paymentTransaction` / `transactionLog` more
|
|
201
|
-
* often than it names a client, and `tx` / `trx` already cover the callback parameter.
|
|
202
|
-
* - `datasource` was unreachable as anyone spells it: `identifierWords("dataSource")` is
|
|
203
|
-
* `["data", "source"]`, so only the all-lowercase form ever matched.
|
|
204
|
-
*
|
|
205
|
-
* A literal source of truth, like every other vocabulary in this package: extending it for
|
|
206
|
-
* a house naming convention is a table edit in exactly one place.
|
|
76
|
+
* The words a Prisma Client binding is spelled with. The callee string is all a classifier
|
|
77
|
+
* sees (effect-plugin.md), and matching is per word (`identifierWords`): `prisma`,
|
|
78
|
+
* `prismaClient`, `readReplicaDb` and `_prisma` count; `cache`, `router`, `items` and
|
|
79
|
+
* `feedback` do not. `tx` / `trx` cover the interactive-transaction callback parameter.
|
|
80
|
+
*
|
|
81
|
+
* Deliberately absent: `client`, which would hand an SDK's `apiClient.users.update(payload)`
|
|
82
|
+
* — spelled exactly like a delegate call — a high-confidence `db.write`; `transaction`,
|
|
83
|
+
* which names a domain noun (`paymentTransaction`) far more often than a client; and
|
|
84
|
+
* `datasource`, which `identifierWords("dataSource")` splits so only the all-lowercase form
|
|
85
|
+
* ever matched. See docs/design/effect-plugin.md.
|
|
207
86
|
*/
|
|
208
87
|
declare const PRISMA_CLIENT_WORDS_LIST: readonly ["prisma", "db", "database", "orm", "tx", "trx"];
|
|
209
88
|
type PrismaClientWord = (typeof PRISMA_CLIENT_WORDS_LIST)[number];
|
|
@@ -211,44 +90,13 @@ declare const PRISMA_CLIENT_WORDS: ReadonlySet<PrismaClientWord>;
|
|
|
211
90
|
/** True when `segment` spells a word this package recognizes as a Prisma client binding. */
|
|
212
91
|
declare function namesPrismaClient(segment: string): boolean;
|
|
213
92
|
/**
|
|
214
|
-
* The most arguments a Prisma call takes before it stops looking like Prisma's own API
|
|
215
|
-
*
|
|
216
|
-
*
|
|
217
|
-
* nothing at all. `$transaction` takes two: the callback form carries an options object
|
|
218
|
-
* (`$transaction(fn, { timeout })`), while the array form takes one.
|
|
93
|
+
* The most arguments a Prisma call takes before it stops looking like Prisma's own API: a
|
|
94
|
+
* delegate method takes one options object or nothing; `$transaction(fn, { timeout })`
|
|
95
|
+
* takes two.
|
|
219
96
|
*/
|
|
220
97
|
declare const PRISMA_DELEGATE_MAX_ARGUMENTS = 1;
|
|
221
98
|
declare const PRISMA_TRANSACTION_MAX_ARGUMENTS = 2;
|
|
222
|
-
/**
|
|
223
|
-
* How much the call backs the classification its method name suggests.
|
|
224
|
-
*
|
|
225
|
-
* `high` needs every signal to agree: the receiver segment names a client binding, the
|
|
226
|
-
* receiver is a binding at all rather than a collapsed expression, and the call takes no
|
|
227
|
-
* more arguments than the API allows. Anything else is `medium` — the effect is still
|
|
228
|
-
* recorded, with the uncertainty stated:
|
|
229
|
-
*
|
|
230
|
-
* - **An unrecognized receiver** is either a binding this plugin cannot place by name (a
|
|
231
|
-
* house convention, a client reached through a wrapper) or an unrelated object that
|
|
232
|
-
* happens to share the verb. A syntactic classifier cannot separate those two without
|
|
233
|
-
* the binding table it has no access to, so it says so in `confidence` rather than
|
|
234
|
-
* picking one and being confidently wrong half the time. `medium` is the same tier
|
|
235
|
-
* `@aburi/framework-express` uses for a route that matches the shape without an import
|
|
236
|
-
* anchor.
|
|
237
|
-
* - **A dynamic receiver** (`getClient().user.create()`, `clients[0].user.create()`) is
|
|
238
|
-
* capped at `medium` whatever it is spelled: normalization collapsed an expression down
|
|
239
|
-
* to a name, so the name in `target` is not a binding and reading it as one would
|
|
240
|
-
* manufacture evidence out of a call the language plugin already flagged as unresolvable
|
|
241
|
-
* (`CallCandidate.dynamicReceiver`).
|
|
242
|
-
* - **An argument list longer than the API takes** is evidence against, not proof:
|
|
243
|
-
* `argumentCount` comes from a syntactic walk, and this classifier is the first thing to
|
|
244
|
-
* read it as a signature. Treating an overflow as "not a Prisma call" would let one
|
|
245
|
-
* miscount erase a real write and log nothing — the failure mode with no trace. So it
|
|
246
|
-
* costs the tier instead, which is this module's own rule applied to its own inputs.
|
|
247
|
-
*
|
|
248
|
-
* A literal first argument is the one shape that is *not* a tier question, and it is not
|
|
249
|
-
* decided here: `prisma.user.delete("u1")` is a type error rather than a Prisma call, so
|
|
250
|
-
* `classifyPrismaCall` rejects it outright.
|
|
251
|
-
*/
|
|
99
|
+
/** `receiverConfidence` under this package's client vocabulary. */
|
|
252
100
|
declare function classificationConfidence(clientSegment: string | undefined, call: CallCandidate, maxArguments: number): Confidence;
|
|
253
101
|
//#endregion
|
|
254
102
|
export { EFFECTS_PRISMA_DERIVED_BY_PREFIX, EFFECTS_PRISMA_PLUGIN_NAME, PRISMA_CLIENT_WORDS, PRISMA_DELEGATE_MAX_ARGUMENTS, PRISMA_READ_METHODS, PRISMA_TRANSACTION_MAX_ARGUMENTS, PRISMA_TRANSACTION_METHOD, PRISMA_WRITE_METHODS, type PrismaClientWord, PrismaEffectsPlugin, type PrismaReadMethod, type PrismaTransactionMethod, type PrismaWriteMethod, classificationConfidence, classifyPrismaCall, effectsPrismaManifest, hasPrismaImport, isPrismaReadMethod, isPrismaTransactionMethod, isPrismaWriteMethod, namesPrismaClient, prismaEffectsPlugin };
|
package/dist/index.mjs
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
import{assertNonEmptySegments as e,
|
|
1
|
+
import{assertNonEmptySegments as e,defineEffectsManifest as t,hasLiteralFirstArgument as n,hasMatchingImport as r,identifierMentions as i,receiverConfidence as a}from"@aburi/plugin-registry/plugin-input";import{COMPUTED_TARGET_SEGMENT as o}from"@aburi/types";const s=`effects-prisma`,c=`effects-plugin:prisma`,l=new Set([`@prisma/client`,`@prisma/client/edge`]);function u(e){return l.has(e)}function d(e,t){return r(e,{plugin:s,filePath:t},u)}const f=[`findUnique`,`findUniqueOrThrow`,`findFirst`,`findFirstOrThrow`,`findMany`,`count`,`aggregate`,`groupBy`],p=[`create`,`createMany`,`createManyAndReturn`,`update`,`updateMany`,`updateManyAndReturn`,`upsert`,`delete`,`deleteMany`],m=new Set(f),h=new Set(p),g=`$transaction`;function _(e){return m.has(e)}function v(e){return h.has(e)}function y(e){return e===g}const b=new Set([`prisma`,`db`,`database`,`orm`,`tx`,`trx`]);function x(e){return i(e,b)}const S=1,C=2;function w(e,t,n){return a(e,t,n,x)}function T(t,r){let i={plugin:s,filePath:r.file.path},{segments:a,last:l}=e(t.target,i);if(!d(r.file.imports,r.file.path))return null;if(y(l))return a.length<2||n(t)?null:{effectId:`db.transaction`,confidence:w(a.at(-2),t,2),derivedBy:`${c}:tx`};if(a.length<3||n(t))return null;let u=a.at(-3);if(u!==void 0&&a.at(-2)===o&&!x(u))return null;let f=w(u,t,1);return _(l)?{effectId:`db.read`,confidence:f,derivedBy:`${c}:read`}:v(l)?{effectId:`db.write`,confidence:f,derivedBy:`${c}:write`}:null}const E=t(s,c);var D=class{manifest=E;async init(e){}classify(e,t){return T(e,t)}};const O=new D;export{c as EFFECTS_PRISMA_DERIVED_BY_PREFIX,s as EFFECTS_PRISMA_PLUGIN_NAME,b as PRISMA_CLIENT_WORDS,S as PRISMA_DELEGATE_MAX_ARGUMENTS,m as PRISMA_READ_METHODS,C as PRISMA_TRANSACTION_MAX_ARGUMENTS,g as PRISMA_TRANSACTION_METHOD,h as PRISMA_WRITE_METHODS,D as PrismaEffectsPlugin,w as classificationConfidence,T as classifyPrismaCall,E as effectsPrismaManifest,d as hasPrismaImport,_ as isPrismaReadMethod,y as isPrismaTransactionMethod,v as isPrismaWriteMethod,x as namesPrismaClient,O as prismaEffectsPlugin};
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@aburi/effects-prisma",
|
|
3
|
-
"version": "0.4.
|
|
3
|
+
"version": "0.4.1",
|
|
4
4
|
"description": "Aburi Prisma effects plugin: classifies prisma.<model>.<verb> and prisma.$transaction call expressions into core db.read / db.write / db.transaction effects",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"author": "kage1020",
|
|
@@ -32,15 +32,16 @@
|
|
|
32
32
|
"access": "public"
|
|
33
33
|
},
|
|
34
34
|
"dependencies": {
|
|
35
|
-
"@aburi/plugin-registry": "0.
|
|
36
|
-
"@aburi/types": "0.
|
|
35
|
+
"@aburi/plugin-registry": "0.5.0",
|
|
36
|
+
"@aburi/types": "0.5.0"
|
|
37
37
|
},
|
|
38
38
|
"devDependencies": {
|
|
39
39
|
"@types/node": "^26.0.1",
|
|
40
40
|
"tsdown": "^0.22.3",
|
|
41
41
|
"typescript": "^6.0.3",
|
|
42
42
|
"vitest": "^4.1.11",
|
|
43
|
-
"@aburi/lang-typescript": "0.
|
|
43
|
+
"@aburi/lang-typescript": "0.5.0",
|
|
44
|
+
"@aburi/test-support": "0.0.1"
|
|
44
45
|
},
|
|
45
46
|
"scripts": {
|
|
46
47
|
"build": "tsdown",
|