docs: add product plan for CLI plugin system #114
Draft
Conversation
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
Introduces comprehensive design document covering: - Plugin structure (entities + BE functions) - Host app configuration format - Extension mechanism for schemas and functions - Plugin installation flow from multiple sources - CLI commands for plugin management - Deploy behavior with plugin merging - Security considerations and permissions model
Contributor
🚀 Package Preview Available!Install this PR's preview build with npm: npm i @base44-preview/cli@0.0.17-pr.114.61b57b5Prefer not to change any import paths? Install using npm alias so your code still imports npm i "base44@npm:@base44-preview/cli@0.0.17-pr.114.61b57b5"Or add it to your {
"dependencies": {
"base44": "npm:@base44-preview/cli@0.0.17-pr.114.61b57b5"
}
}
Preview published to npm registry — try new features instantly! |
Research on how other platforms handle plugins: - Terraform: Own registry with GPG signing - VS Code: Marketplace with verified publisher badges - Figma: Own marketplace with human review - Shopify/Heroku/Gatsby: npm-only approach - Strapi/Backstage: Hybrid npm + own marketplace - WordPress: SVN with mandatory human review Includes recommendation for phased hybrid approach: 1. npm-first MVP 2. Base44 registry for discoverability 3. Enterprise features (private registry, signing)
Updates product design based on competitive analysis: - Add phased rollout summary to executive summary - Update plugin structure to use package.json + base44.plugin.jsonc - Make npm the primary distribution channel (Phase 1) - Add phase indicators to CLI commands section - Update installation flow for npm-first resolution - Update lock file to reference npm registry - Update publishing workflow: npm publish first, then optional Base44 registry registration (Phase 2+) This aligns with patterns from Shopify CLI, Heroku CLI, and Strapi while planning for future Base44 registry.
Updates to clarify core vs optional features: - Entity extensions: Core feature (Phase 1) - Function hooks/wrappers: Optional, future consideration Changes: - Update Section 4 header with core vs optional callout - Mark Section 4.2 (function hooks) as optional/future - Mark Section 4.3 (function wrapping) as optional/future - Update plugin config to comment out function hooks - Update extensions directory to show entity-only structure - Update summary table with status column (Core/Optional/Phase 3) - Update architecture diagram to show "Entity Extensions (Core)" For Phase 1, host apps can create their own functions that call plugin functions if custom logic is needed.
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.
Introduces comprehensive design document covering:
Description
Related Issue
Type of Change
Changes Made
Testing
npm test)Checklist
Additional Notes