Conversation
Greptile SummaryThis PR adds a new "Appwrite vs PocketBase" comparison blog post with cover image and cache entry. The content is well-structured and covers deployment, database, auth, functions, realtime, messaging, and SDK differences accurately — with one author attribution issue and one factual inaccuracy to resolve before publishing.
Confidence Score: 3/5Not safe to merge until the author attribution is confirmed correct and the ES5 runtime claim is updated. The author field almost certainly contains a copy-paste error (aditya-oberai instead of aishwari), which would publish the article under the wrong name. The ES5 JSVM description is a factual inaccuracy that could mislead developers evaluating PocketBase. Both are pre-merge fixes. +page.markdoc — author field and PocketBase runtime description need attention. Important Files Changed
Reviews (1): Last reviewed commit: "new comparison blog" | Re-trigger Greptile |
| date: 2026-04-20 | ||
| cover: /images/blog/appwrite-vs-pocketbase-which-open-source-backend-fits-your-project/cover.png | ||
| timeToRead: 5 | ||
| author: aditya-oberai |
There was a problem hiding this comment.
Author field doesn't match PR submitter
The author is set to aditya-oberai, but this PR was submitted by aishwaripahwa12, whose registered author slug is aishwari. Every other comparison post authored by the same submitter uses their own slug. If this is intentional ghostwriting, no change is needed — but if it was copied from a template and not updated, the author attribution will be incorrect on the published post.
| author: aditya-oberai | |
| author: aishwari |
|
|
||
| This is where the two platforms diverge most clearly. | ||
|
|
||
| PocketBase extends through **JavaScript hooks** running in an embedded ES5 JSVM or by using PocketBase as a Go package and compiling your own binary. JavaScript hooks handle scheduled jobs, custom routes, and record lifecycle events. They are limited to CommonJS modules with no npm packages and no arbitrary runtimes. |
There was a problem hiding this comment.
PocketBase JSVM is ES6, not ES5
The post describes PocketBase's runtime as "an embedded ES5 JSVM." According to the official PocketBase docs, the embedded goja engine "has most of ES6 functionality already implemented." Calling it ES5 may mislead readers about what JavaScript features are usable in hooks (arrow functions, template literals, destructuring, etc. all work).
New comparison blog