Repository navigation
Conversation
Contributor
📦 Bundle size reportCompared against
|
| dist | raw | gzip |
|---|---|---|
| JS (runtime) | 1.4 MB (-601 B) | 500 KB (+862 B) |
| Type declarations | 482 KB (-1.2 KB) | 174 KB (-424 B) |
| Source maps | 2.7 MB (-1.3 KB) | 930 KB (+1.4 KB) |
| Other | 11 KB | 3.7 KB |
| Total | 4.6 MB (-3.1 KB) | 1.6 MB (+1.8 KB) |
Per-entry composition (own code — deps external (as shipped))
| Entry | Initial (gz) | Lazy (gz) | Total (gz) | node_modules (min) | Own code (min) |
|---|---|---|---|---|---|
. |
118 KB (+103 B) | 2.4 KB | 121 KB (+103 B) | external | 378 KB (+281 B) |
./beta |
118 KB (+3.1 KB) | 4.5 KB (+4.1 KB) | 123 KB (+7.1 KB) | external | 356 KB (+14 KB) |
./testing |
47 KB (+41 B) | 38 KB (+118 B) | 85 KB (+159 B) | external | 246 KB (+281 B) |
./tsdown |
630 B (+110 B) | 0 B | 630 B (+110 B) | external | 1.0 KB (+233 B) |
./type-generator |
31 KB (-59 B) | 0 B | 31 KB (-59 B) | external | 89 KB (-292 B) |
Chunks:
| Entry | Chunk | Load | Size (gz) |
|---|---|---|---|
. |
index.js |
initial | 114 KB |
. |
utils.js |
initial | 4.6 KB |
. |
remote-tunnel-manager.js |
lazy | 2.4 KB |
./beta |
beta.js |
initial | 92 KB |
./beta |
stream-manager.js |
initial | 5.9 KB |
./beta |
define-schema.js |
initial | 5.8 KB |
./beta |
service-context.js |
initial | 4.3 KB |
./beta |
modular.js |
initial | 3.6 KB |
./beta |
databricks.js |
initial | 3.3 KB |
./beta |
wide-event-emitter.js |
initial | 2.8 KB |
./beta |
client.js |
initial | 645 B |
./beta |
index.js |
initial | 20 B |
./beta |
index.js |
lazy | 4.0 KB |
./beta |
supervisor-api.js |
lazy | 201 B |
./beta |
databricks.js |
lazy | 186 B |
./beta |
index.js |
lazy | 124 B |
./testing |
manifest.js |
initial | 34 KB |
./testing |
index.js |
initial | 10 KB |
./testing |
wide-event-emitter.js |
initial | 2.9 KB |
./testing |
index.js |
lazy | 34 KB |
./testing |
remote-tunnel-manager.js |
lazy | 2.4 KB |
./testing |
utils.js |
lazy | 1.8 KB |
./tsdown |
index.js |
initial | 630 B |
./type-generator |
index.js |
initial | 31 KB |
@databricks/appkit-ui
npm tarball (packed): 390 KB (-38 KB) — gzipped download (dist + bin; excludes release-only docs/NOTICE).
| dist | raw | gzip |
|---|---|---|
| JS (runtime) | 427 KB (-29 KB) | 145 KB (-12 KB) |
| Type declarations | 249 KB (-33 KB) | 92 KB (-12 KB) |
| Source maps | 831 KB (-75 KB) | 279 KB (-27 KB) |
| CSS | 16 KB | 3.2 KB |
| Total | 1.5 MB (-137 KB) | 519 KB (-52 KB) |
Per-entry composition (consumer bundle — deps bundled, peerDeps external)
| Entry | Initial (gz) | Lazy (gz) | Total (gz) | node_modules (min) | Own code (min) |
|---|---|---|---|---|---|
./js |
5.3 KB | 49 KB | 55 KB | 208 KB | 14 KB |
./js/beta |
2.4 KB (-1.1 KB) | 0 B | 2.4 KB (-1.1 KB) | 0 B | 5.3 KB (-4.1 KB) |
./react |
441 KB | 49 KB | 489 KB | 1.4 MB | 179 KB |
./react/beta |
13 KB (-3.1 KB) | 0 B | 13 KB (-3.1 KB) | 25 KB (-18 B) | 12 KB (-10 KB) |
Chunks:
| Entry | Chunk | Load | Size (gz) |
|---|---|---|---|
./js |
index.js |
initial | 5.2 KB |
./js |
chunk |
initial | 120 B |
./js |
apache-arrow |
lazy | 49 KB |
./js/beta |
beta.js |
initial | 2.4 KB |
./react |
index.js |
initial | 439 KB |
./react |
tslib |
initial | 2.1 KB |
./react |
apache-arrow |
lazy | 49 KB |
./react/beta |
beta.js |
initial | 13 KB |
Contributor
🤖 AppKit PR bot🔬 Run evalsStart an eval for this PR from the evals-monitor app: Go to Evals Monitor → 📦 Try this PR's app templateScaffolds a new app from this PR's SDK build. Run it in any folder (requires the GitHub CLI — gh run download 44777343257 -R databricks/appkit -n appkit-template-0.101.0-pr.81ef51e-stack-database-stable-06-serve-operations-692 -D appkit-pr-692 \
&& unzip -o "appkit-pr-692/appkit-template-0.101.0-pr.81ef51e-stack-database-stable-06-serve-operations-692.zip" -d "appkit-pr-692" \
&& databricks apps init --template "appkit-pr-692"The template pins |
ditadi
force-pushed
the
stack/database-stable/06-serve-operations
branch
from
October 26, 2026 10:41
f72c9a7 to
8a9f21c
Compare
ditadi
marked this pull request as ready for review
October 28, 2026 11:05
ditadi
force-pushed
the
stack/database-stable/06-serve-operations
branch
from
November 3, 2026 13:01
4b113fa to
2fd1455
Compare
ditadi
force-pushed
the
stack/database-stable/06-serve-operations
branch
from
November 3, 2026 13:47
2fd1455 to
30d4a43
Compare
ditadi
requested review from
MarioCadenas
and removed request for
atilafassina
November 3, 2026 13:55
ditadi
force-pushed
the
stack/database-stable/06-serve-operations
branch
from
November 3, 2026 15:18
30d4a43 to
a483f29
Compare
This was referenced Nov 3, 2026
ditadi
force-pushed
the
stack/database-stable/06-serve-operations
branch
from
November 4, 2026 19:15
a483f29 to
4fb8105
Compare
ditadi
force-pushed
the
stack/database-stable/06-serve-operations
branch
2 times, most recently
from
November 6, 2026 10:49
2f36a19 to
5fef7c8
Compare
ditadi
force-pushed
the
stack/database-stable/06-serve-operations
branch
from
November 17, 2026 13:57
cbeeec2 to
b6887df
Compare
ditadi
force-pushed
the
stack/database-stable/06-serve-operations
branch
from
November 20, 2026 10:04
b6887df to
eae9822
Compare
ditadi
force-pushed
the
stack/database-stable/06-serve-operations
branch
2 times, most recently
from
November 20, 2026 14:20
8fe680e to
32310be
Compare
ditadi
force-pushed
the
stack/database-stable/06-serve-operations
branch
from
November 20, 2026 14:27
32310be to
88de7f0
Compare
ditadi
force-pushed
the
stack/database-stable/06-serve-operations
branch
3 times, most recently
from
November 20, 2026 16:39
65584c8 to
b540231
Compare
Base automatically changed from
stack/database-stable/05-client-operations
to
main
November 20, 2026 16:50
database({ routes }) mounts the generated registry under
/api/database/operations/<name>; without routes the plugin serves no
HTTP endpoint. The table routes, the api and crudRoutes options, the
entity client and hooks, and their HTTP facets are removed.
The playground, template, and docs move to named operations. The
playground writes a note and its event in one transaction, and only
the author may change or delete the note.
Signed-off-by: ditadi <victordperd@gmail.com>
Signed-off-by: ditadi <victordperd@gmail.com>
Signed-off-by: ditadi <victordperd@gmail.com>
Signed-off-by: ditadi <victordperd@gmail.com>
The plugin validates and serves operations without the schema's table set, and the playground declares an output on boards.create, notes.create, and notes.update while notes.delete answers no body. The database guide drops the entity field and the default-output table, says that every callback, the resource lookup included, receives the actor, and states that private() does not sanitize an operation's output. The table contract and column codecs that only default outputs used go with them, along with the shared WireOutput type. Co-authored-by: Isaac <no-reply@databricks.com> Signed-off-by: ditadi <victordperd@gmail.com>
The upgraded instrumentation names the server by server.port, not http.host, so the fake workspace's spans are dropped by port. [#tern:skip] Co-authored-by: Isaac <no-reply@databricks.com> Signed-off-by: ditadi <victordperd@gmail.com>
The guide states the origin check first, the 30-second reuse of a verified token, proxy write failures as unknown outcomes, and which files discovery skips. Co-authored-by: Isaac <no-reply@databricks.com> Signed-off-by: ditadi <victordperd@gmail.com>
The watcher test ran its server without the development export condition, so shared resolved to its unbuilt dist and the test failed on a fresh install. The child now gets the condition through NODE_OPTIONS, which reaches the node process that tsx watch spawns. Co-authored-by: Isaac <no-reply@databricks.com> Signed-off-by: ditadi <victordperd@gmail.com>
…hema Operations in server/database/routes/ still need config/database/schema.ts with an explicit schema, because type generation and the generated registry import it. The guide says so and shows a one-line re-export for a different layout. Co-authored-by: Isaac <no-reply@databricks.com> Signed-off-by: ditadi <victordperd@gmail.com>
Writes without Origin or Sec-Fetch-Site are now refused before the caller is identified, so the unauthenticated and absolute-form cases send what a same-origin page sends and still reach the identity check. Co-authored-by: Isaac <no-reply@databricks.com> Signed-off-by: ditadi <victordperd@gmail.com>
…licy failures An answer is bounded by 5 MiB and an unusable one is logged, a write must carry Origin or Sec-Fetch-Site, a database failure inside a policy fails the request instead of refusing it, and a 403 from the identity check is logged. Co-authored-by: Isaac <no-reply@databricks.com> Signed-off-by: ditadi <victordperd@gmail.com>
A database failure inside a policy answers 503 or 500, and a database permission error still refuses. A policy whose queries run only for an existing record can reveal that record while the database is failing. Co-authored-by: Isaac <no-reply@databricks.com> Signed-off-by: ditadi <victordperd@gmail.com>
The client now opens a new session when someone signs in after a 401, so queries that showed a sign-in error ask again. Co-authored-by: Isaac <no-reply@databricks.com> Signed-off-by: ditadi <victordperd@gmail.com>
The template's build now runs `appkit generate-types` under `NODE_ENV=production`, so a custom build that calls the command needs the same setting to fail on an operation without authorization. Co-authored-by: Isaac <no-reply@databricks.com> Signed-off-by: ditadi <victordperd@gmail.com>
ditadi
force-pushed
the
stack/database-stable/06-serve-operations
branch
from
November 20, 2026 16:50
b540231 to
6d0c849
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What did you change, and why?
Authored operations are now the only database HTTP surface.
database()discovers the generated registry forserver/database/routes/, so an app using the conventional layout no longer importsroutes.gen.tsin its server entry.database()discovers operations,database({ routes: false })keeps server-side access only, anddatabase({ routes: customRoutes })uses an explicit registry.appkitServerConfig()build includes the registry, schema, and operation modules automatically. Production discovery loads the compiled registry beside the server entry, including custom output directories. Clean builds remove stale registries when sources are deleted.tsx watchtrack routes, shared row schemas, and policies; first-route additions and last-route deletions reload correctly. Production uses the compiled registry without generating files.apioption, thecrudRoutescheck, the entity client and hooks, the CRUD HTTP facets, and theDatabricksAppKitDatabaseRegistryglobal, with no compatibility layer.skipTokenfor dependent note reads. Its row-answering operations declare explicit outputs withoutauthor_email, andnotes.deleteanswers no body. Documentation explains omitted-input and omitted-output semantics, explicit schemas, that.private()does not filter anoutput, and that a policy'sresourcelookup receivesactor.This replaces the beta database HTTP API. Operations without input schemas accept no parameters, and operations without output schemas answer no body.
Interface
An explicit schema overrides conventional schema discovery. With an explicit routes registry, the schema must be the same object the registry loads. Custom server builds must include the registry entry beside their server using the same file extension, or import and pass the registry explicitly.
Removed without a compatibility layer:
database({ api }), its AutoCRUD configuration types, and routes under/api/database/<table>.databaseApi.list,get,create,update, andremove; the entity CRUD hooks; andinvalidateDatabaseReads.DatabricksAppKitDatabaseRegistryglobal that the entity hooks read.crud/codecs.ts,compileCrudTables) and the sharedWireOutputtype, which lost their last consumers.Validation
tsx watchtest below) and the playground smoke test (10) pass.tsx watch+ Vite test covers schema-only startup, first route creation, route edits, shared schema edits, added routes, deletions, and final route removal without a restart loop.pnpm build,pnpm docs:build,pnpm check:fix, andpnpm -r typecheckpass.Live Databricks Apps identity and Lakebase were not exercised. The docs build reports an existing broken anchor in custom-plugin telemetry documentation; it completes successfully.
Stack
#683 → #687 → #688 → #689 → #690 → #691 → #692
Design: #683. Previous layer: #691.
Review feedback:
refactor(appkit): migrate operations to explicit outputsmigrates the playground, tests, and guide, and removes the orphaned codecs.Review feedback (round 2): the
hooksguard from #687 stays, pointing to named operations.docs(appkit): follow the operation review fixes in the guidedocuments these behaviors:Restack: the conflicts with main's #712 (
skipBodyParsingpatterns, kept alongside the operation prefixes) and #680 (design plugin exports) are resolved. Integration spans are filtered under the stable HTTP conventions.Stack created with GitHub Stacks CLI • Give Feedback 💬